<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:"Cambria Math"}
@font-face
        {font-family:Calibri}
@font-face
        {font-family:"Georgia Pro"}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
        {color:#0563C1;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:#954F72;
        text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif}
p.msonormal0, li.msonormal0, div.msonormal0
        {margin-right:0in;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif}
span.EmailStyle19
        {font-family:"Calibri",sans-serif;
        color:windowtext}
span.EmailStyle20
        {font-family:"Georgia Pro",serif;
        color:windowtext}
span.EmailStyle21
        {font-family:"Georgia Pro",serif;
        color:windowtext}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
ol
        {margin-bottom:0in}
ul
        {margin-bottom:0in}
-->
</style><style type="text/css" id="owaParaStyle"></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Arial;color: #000000;font-size: 10pt;"><font size="2">What is not quite clear to me from the proposal is whether you could only use the very limited terms in the RDA element "type of binding" encoding scheme or whether
 you could use terms from any suitable vocabulary encoding scheme. </font>
<div><font size="2"><br>
</font></div>
<div><font size="2">Here the five terms that are in the RDA encoding scheme:<br>
</font>
<div><font size="2"><span style="background-color: rgb(255, 255, 255);"><br>
</span></font></div>
<div><font size="2"><span style="background-color: rgb(255, 255, 255);">closed ring<br>
</span><span style="background-color: rgb(255, 255, 255);">hardback<br>
</span><span style="background-color: rgb(255, 255, 255);">open ring<br>
</span><span style="background-color: rgb(255, 255, 255);">paperback<br>
</span><span style="background-color: rgb(255, 255, 255);">spiral</span></font></div>
<div><b><font size="2"><br>
</font></b></div>
<div><font size="2">If </font><span style="font-size: small;">this was made applicable to copy-specific data, and </span><span style="font-size: small;">we were not limited to the RDA encoding scheme but we could use any encoding scheme, for instance terms
 in rbbin, should sub-field $l not be made repeatable? (As currently proposed, it is not; although all existing sub-fields a-o in 340 are).</span></div>
<div><font size="2"><br>
</font></div>
<div><font size="2">Kind regards,</font></div>
<div><font size="2">Iris</font></div>
<div><font size="2"><br>
</font>
<div>
<div style="font-size:13px; font-family:Tahoma">
<div style="margin:0px"><font face="Arial,sans-serif">------------------------------------------------------</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">Iris O'Brien </font></div>
<div style="margin:0px"><font face="Arial,sans-serif">Early Printed Collections Cataloguing and Processing Manager</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">The British Library</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">St Pancras</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">96 Euston Road</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">London</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">NW1 2DB</font></div>
<div style="margin:0px"><font face="Arial,sans-serif">Tel.: +44 (0)20 7412 7731 </font>
</div>
<div style="margin:0px"><font face="Arial,sans-serif">E-mail: iris.o'brien@bl.uk</font></div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF187369" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> DCRM-L [dcrm-l-bounces@lib.byu.edu] on behalf of Lapka, Francis [francis.lapka@yale.edu]<br>
<b>Sent:</b> 03 June 2020 13:36<br>
<b>To:</b> 'dcrm-l@lib.byu.edu'<br>
<b>Subject:</b> [DCRM-L] MARC revision proposals<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Hi all.</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">At a skim, I see three items of at least passing interest on the agenda of the MARC Advisory Committee (see full email below):</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<ul type="disc" style="margin-top:0in">
<li class="MsoNormal" style=""><a href="http://www.loc.gov/marc/mac/2020/2020-04.html" target="_blank" rel="noopener noreferrer">Proposal No. 2020-04</a>: Defining a New Subfield for Illustrative Content in Field 340 of the MARC 21 Bibliographic Format</li></ul>
<p class="MsoNormal"> </p>
<ul type="disc" style="margin-top:0in">
<li class="MsoNormal" style=""><a href="http://www.loc.gov/marc/mac/2020/2020-06.html" target="_blank" rel="noopener noreferrer">Proposal No. 2020-06</a>: Defining a New Field for Manifestation Statements in the MARC 21 Bibliographic Format</li></ul>
<p class="MsoNormal"> </p>
<ul type="disc" style="margin-top:0in">
<li class="MsoNormal" style=""><a href="http://www.loc.gov/marc/mac/2020/2020-dp17.html" target="_blank" rel="noopener noreferrer">Discussion Paper No. 2020-DP17</a>: Recording the Type of Binding for Manifestations in the MARC 21 Bibliographic Format</li></ul>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">I’m particularly interested in the thoughts of list members on the “type of binding” discussion paper. It proposes a new 340 subfield $l for “</span><span style="color:red">A method used to
 bind a published or unpublished manifestation</span><span style="font-family:"Georgia Pro",serif">” – in spirit closely aligned with RDA’s
<a href="https://beta.rdatoolkit.org/en-US_ala-4b9320ad-5cf8-31b7-aad2-7d4b60070bbb" target="_blank" rel="noopener noreferrer">
type of binding element</a>. As framed, the subfield’s scope is limited to manifestations, making it unusable for copy-specific description. How do folks feel about that?</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">I notice now that the
<a href="http://www.loc.gov/marc/bibliographic/bd340.html" target="_blank" rel="noopener noreferrer">
MARC 340 field</a> does not define $5, so that we can’t use any of its subfields for copy-specific data. At a skim, copy-specific data could apply to these subfields, if $5 were defined:</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<ul type="disc" style="margin-top:0in">
<li class="MsoNormal" style=""><span style="font-family:"Georgia Pro",serif">$a - Material base and configuration: to distinguish, for example, between copies on paper or vellum</span></li><li class="MsoNormal" style=""><span style="font-family:"Georgia Pro",serif">$b - Dimensions: for copy-specific heights, etc.</span></li><li class="MsoNormal" style=""><span style="font-family:"Georgia Pro",serif">$g - Color content: for copy-specific hand-coloring</span></li><li class="MsoNormal" style=""><span style="font-family:"Georgia Pro",serif">$l - Type of binding (proposed): for terms describing bespoke bindings</span></li></ul>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Would it be worth proposing a subfield $5?
</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">There’s perhaps a small overlap between this question and those posed in my DCRM-L query from earlier this week (on 655 field migration to BIBFRAME). If we hadn’t used field 655 for years and
 years to record information on binding terms and paper terms – or if we were starting from scratch – would field 340 be better, because its subfields provide a clearer declaration of the specific properties involved?</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Francis</span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> MARC <MARC@LISTSERV.LOC.GOV> <b>On Behalf Of </b>
NDMSO<br>
<b>Sent:</b> Friday, May 29, 2020 6:06 PM<br>
<b>To:</b> MARC@LISTSERV.LOC.GOV<br>
<b>Subject:</b> [MARC] MAC meeting plans -- papers and agenda for MAC Annual meeting available online</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="">After discussions with the MARC Steering Group and the MAC chair, the MAC meeting is set to be virtual on June 30-July 2, 2020.  The meeting will be hosted by the Library of Congress with Matthew Wise, the chair, in the role of
 moderator.  Because of technical considerations, meeting participation will be MAC members and invitees who have an involvement with the paper topics.  However, as usual, the papers are being posted a month in advance of the meeting, so it is especially important
 for users to comment on the issues in the coming weeks before the meeting.  Matthew Wise asks that comments be posted by June 22 so he can do his customary summaries for the MAC members.</p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal">The MAC Annual meeting agenda is available at: </p>
<p class="MsoNormal"><a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2Fan2020_age.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867694987117&sdata=WBtBXNjz%2FYz87i6pCUyu6rdc0GG4fG08ftqStYnuRwI%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/an2020_age.html</a></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b>PROPOSALS</b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Proposal No. 2020-03: Modernization of Field 856 in the </p>
<p class="MsoNormal">MARC 21 Formats</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-03.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867694997111&sdata=vcKIbgwCI6o1r8Ilv%2FCFUmR5JC3yM8rI6LT5DdVNM3c%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-03.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Proposal No. 2020-04: Defining a New Subfield for Illustrative Content</p>
<p class="MsoNormal">in Field 340 of the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-04.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867694997111&sdata=jedOiNZmaB3EpOeC1vj2IFid2R2%2B%2FK9MGJqD%2FT25g%2Bs%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-04.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Proposal No. 2020-05: Renaming Field 345 and Defining New Subfields</p>
<p class="MsoNormal">for Aspect Ratio in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-05.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867694997111&sdata=hZfNrMQvNdxAWAEnbmYl5OFaZ3KwG7GnCSaeHzFvU2o%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-05.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Proposal No. 2020-06: Defining a New Field for Manifestation
</p>
<p class="MsoNormal">Statements in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-06.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695007103&sdata=OO0MAhN%2BbIGEX4EhBNLDLCnUvNhcuScLkjenYopLbOc%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-06.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Proposal No. 2020-07: Recording the Extension Plan for Bibliographic
</p>
<p class="MsoNormal">Works in the MARC 21 Bibliographic and Authority Formats</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-07.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695007103&sdata=qriHlXfEEN00vXNlZZOCr2Kdlxp%2BshdrZY8bt4iisiw%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-07.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">  </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b>DISCUSSION PAPERS</b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP08: Subfields for Recording Date of
</p>
<p class="MsoNormal">Assignment of Dewey Decimal Numbers in the MARC 21 Formats</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp08.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695017100&sdata=LoG%2BGwU%2FU%2Bo4tfgyxt6Ew3bHTw7zpwWOgXgd7UamI0o%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp08.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP09: Chronology-Only Data in Holdings
</p>
<p class="MsoNormal">Fields 853-855 and 863-865</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp09.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695017100&sdata=E%2Fy%2FJ4Ik%2BiTBo0qmfOpjk%2BbZHdCTXW%2BcD9y67xx747Q%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp09.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP10: Changes to Fields 008/21 and
</p>
<p class="MsoNormal">006/04 for Type of Continuing Resource in the MARC 21 </p>
<p class="MsoNormal">Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp10.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695027096&sdata=gZGZdebzQPa%2FRmPUx%2F9BZBxR1%2FkOkDRhRErEtnOc2OI%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp10.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP11: Adding Subfield $0 to Field 022
</p>
<p class="MsoNormal">in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp11.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695027096&sdata=ZjpsLCuWhRjY9zpPTA7AFKmx8YFhWc043MGl69Phrzo%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp11.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP12: Moving Form of Musical Notation
</p>
<p class="MsoNormal">from Field 546 to Field 348 in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp12.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695037085&sdata=WvZjTuOfAtX0INT1IoQpPCRUj923%2BpXwy%2F4pb0slTgw%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp12.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP13: Defining New Subfields in </p>
<p class="MsoNormal">Bibliographic and Authority Field 046 for Expression Dates </p>
<p class="MsoNormal">and Related Elements</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp13.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695037085&sdata=zG0%2F2jnRDimcn8Z0sxjLVPhwh0eQH1EwIa6AjHe1yFg%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp13.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP14: Defining a New Subfield for </p>
<p class="MsoNormal">Sound Content in Field 344 of the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp14.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695037085&sdata=8VN6GxWeMYkuHxE0Qoy8d5R2C6qzJcSZeyDWx4Xr16M%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp14.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP15: Changes to Supplementary </p>
<p class="MsoNormal">Content Information to Accommodate URIs and Notes in the </p>
<p class="MsoNormal">MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp15.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695047079&sdata=f1D8fwu0EzeEh9tklL5LAkxj7dfQgbdvaaPGGxgqpN0%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp15.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP16: Recording the Mode of Issuance
</p>
<p class="MsoNormal">for Manifestations in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp16.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695047079&sdata=YoRrh6suBv0xyCgRRPUoWRuCw9HCNtd7rYeMjcna7og%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp16.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Discussion Paper No. 2020-DP17: Recording the Type of Binding
</p>
<p class="MsoNormal">for Manifestations in the MARC 21 Bibliographic Format</p>
<p class="MsoNormal">(<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fmac%2F2020%2F2020-dp17.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C14b19eb3358b42cb9fc008d8041c7cf9%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637263867695057073&sdata=dKsHLVRxD%2B4N0dRET0Wrbevnzpy6X7hy8DzCoWekl9s%3D&reserved=0" target="_blank" rel="noopener noreferrer">http://www.loc.gov/marc/mac/2020/2020-dp17.html</a>)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">-----------------------------------------------</p>
<p class="MsoNormal">Network Development and MARC Standards Office</p>
<p class="MsoNormal">101 Independence Ave., S.E.</p>
<p class="MsoNormal">Washington, DC 20540-4402 U.S.A.</p>
<p class="MsoNormal">TEL: +1-202-707-6237</p>
<p class="MsoNormal">FAX: +1-202-707-0115</p>
<p class="MsoNormal">NET: [log in to unmask]</p>
<p class="MsoNormal">-----------------------------------------------</p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
 <br>
******************************************************************************************************************</div>
<div><font face="Arial">Experience the British Library online at </font><a href="http://www.bl.uk/"><font face="Arial">www.bl.uk</font></a></div>
<div><font face="Arial"></font></div>
<div><font face="Arial">The British Library’s latest Annual Report and Accounts :
</font><a href="http://www.bl.uk/aboutus/annrep/index.html"><font face="Arial">www.bl.uk/aboutus/annrep/index.html</font></a></div>
<div><font face="Arial"></font></div>
<div><font face="Arial">Help the British Library conserve the world's knowledge. Adopt a Book.
</font><a href="http://www.bl.uk/adoptabook"><font face="Arial">www.bl.uk/adoptabook</font></a></div>
<div><font face="Arial"></font></div>
<div><font face="Arial">The Library's St Pancras site is WiFi - enabled</font></div>
<div></div>
<div>*****************************************************************************************************************</div>
<div></div>
<div><font face="Arial">The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the
</font><a href="mailto:postmaster@bl.uk"><font face="Arial">postmaster@bl.uk</font></a><font face="Arial"> : The contents of this e-mail must not be disclosed or copied without the sender's consent.
</font></div>
<div><font face="Arial"></font></div>
<div><font face="Arial">The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
</font></div>
<div></div>
<div>*****************************************************************************************************************
</div>
<div><font color="#008000"><font face="Arial">Think before you print</font></font></div>
</body>
</html>