<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: Arial Unicode MS;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Palatino Linotype;
}
@font-face {
font-family: @Arial Unicode MS;
}
@font-face {
font-family: @MS Mincho;
}
@page WordSection1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext
}
SPAN.ExampleChar {
FONT-FAMILY: "Courier New"
}
P.Example {
TEXT-INDENT: -0.2in; MARGIN: 12pt 0in 0pt 0.7in; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt
}
LI.Example {
TEXT-INDENT: -0.2in; MARGIN: 12pt 0in 0pt 0.7in; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt
}
DIV.Example {
TEXT-INDENT: -0.2in; MARGIN: 12pt 0in 0pt 0.7in; FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt
}
SPAN.ExamplecommentChar {
FONT-FAMILY: "Palatino Linotype","serif"
}
P.Examplecomment {
MARGIN: 0in 0in 0pt 1in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 10pt
}
LI.Examplecomment {
MARGIN: 0in 0in 0pt 1in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 10pt
}
DIV.Examplecomment {
MARGIN: 0in 0in 0pt 1in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 10pt
}
SPAN.NormalparagraphChar {
FONT-FAMILY: "Palatino Linotype","serif"
}
P.Normalparagraph {
MARGIN: 12pt 0in 0pt; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt
}
LI.Normalparagraph {
MARGIN: 12pt 0in 0pt; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt
}
DIV.Normalparagraph {
MARGIN: 12pt 0in 0pt; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt
}
SPAN.Header3Char {
FONT-FAMILY: "Palatino Linotype","serif"; FONT-WEIGHT: bold
}
P.Header3 {
PAGE-BREAK-AFTER: avoid; TEXT-INDENT: -0.55in; MARGIN: 12pt 0in 0pt 0.55in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt; FONT-WEIGHT: bold
}
LI.Header3 {
PAGE-BREAK-AFTER: avoid; TEXT-INDENT: -0.55in; MARGIN: 12pt 0in 0pt 0.55in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt; FONT-WEIGHT: bold
}
DIV.Header3 {
PAGE-BREAK-AFTER: avoid; TEXT-INDENT: -0.55in; MARGIN: 12pt 0in 0pt 0.55in; FONT-FAMILY: "Palatino Linotype","serif"; FONT-SIZE: 11pt; FONT-WEIGHT: bold
}
SPAN.normalbold {
FONT-WEIGHT: bold
}
P.Examplecommentpreface {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.Examplecommentpreface {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.Examplecommentpreface {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
SPAN.ExamplecommentprefaceChar {
FONT-FAMILY: "Times New Roman","serif"
}
.MsoChpDefault {
}
DIV.WordSection1 {
}
</style>
<meta name="GENERATOR" content="MSHTML 8.00.7600.16930">
<style id="owaTempEditStyle"></style><style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" ocsi="x">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: x-small">
<div>Hello, </div>
<div><font face="tahoma"> This is such a sensible solution, not only to incorporate the text of 0G10 into 0G4, but also using its heading as the label for the rules under 0G4.4. The editors of DCRM(M) have mentioned the unusual placement of these two rules
more than once, but we did not go so far as to consider suggesting that it be changed. (Good for Erin--and many thanks--for figuring this out so well and making the change so clear.) I just now had a chance to read through this issue, so have not discussed
this (yet) with my team, but I hope they are reading this and agreeing that it works much better with the suggested change. </font></div>
<div><font face="tahoma"><font face="tahoma"> </font>I have been finalizing the 5B draft of DCRM (Music) and this could not have come at a better time. I am tempted to go ahead and just make the move now, without waiting for the official sanction. (I'll see
how the timing goes...)</font></div>
<div><font face="tahoma"> Thanks again, Jain</font></div>
<div> </div>
<div><font size="2" face="Californian FB"><span style="FONT-FAMILY: 'Californian FB','serif'; COLOR: #1f497d"></span><span style="FONT-FAMILY: 'Californian FB','serif'; COLOR: blue; FONT-SIZE: 12pt">Jain Fletcher<br>
Principal Cataloger & Head, Cataloging Section<br>
</span><span style="FONT-FAMILY: 'Californian FB','serif'; COLOR: blue; FONT-SIZE: 12pt"><span style="FONT-FAMILY: 'Californian FB','serif'; COLOR: blue; FONT-SIZE: 12pt"><font face="californian fb">Collection Management Division</font> <br>
</span>Library Special Collections <br>
Young Research Library - UCLA Box 951575<br>
Los Angeles, CA 90095-1575</span><span style="FONT-FAMILY: 'Times New Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"></span></div>
<div>
<div>
<div class="WordSection1">
<blockquote style="MARGIN-RIGHT: 0px" dir="ltr">
<p style="MARGIN-LEFT: 0.5in" class="MsoNormal"><span style="FONT-FAMILY: 'Californian FB','serif'; COLOR: blue; FONT-SIZE: 12pt">v: (310) 794-4096<br>
f: (310) 206-1864<br>
e: </span><span style="FONT-FAMILY: 'Times New Roman','serif'; COLOR: blue; FONT-SIZE: 10pt"><a title="mailto:jfletchr@library.ucla.edu" href="mailto:jfletchr@library.ucla.edu"><span style="FONT-FAMILY: 'Californian FB','serif'; FONT-SIZE: 12pt"><font color="#0000ff">jfletchr@library.ucla.edu</font></span></a>
</span><span style="FONT-FAMILY: 'Times New Roman','serif'; COLOR: blue; FONT-SIZE: 12pt"></span></p>
</blockquote>
</div>
</font></div>
</div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma"></font> </div>
<div style="DIRECTION: ltr" id="divRpF308250">
<hr tabindex="-1">
<font color="#000000" size="2" face="Tahoma"><b>From:</b> dcrm-l-bounces@lib.byu.edu [dcrm-l-bounces@lib.byu.edu] On Behalf Of Erin Blake [EBlake@folger.edu]<br>
<b>Sent:</b> Monday, March 19, 2012 7:23 PM<br>
<b>To:</b> DCRM-L (dcrm-l@lib.byu.edu)<br>
<b>Subject:</b> [DCRM-L] DPC: Unite area 0 rules for spacing under 0G4<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Here's the formal "discussion of proposed change" to DCRM previously alluded to. Following standard DPC procedure (http://wikis.ala.org/acrl/index.php/DCRM_Editorial_Guidelines#Discussion_of_Proposed_Changes) this will be open for discussion
for at least one week (and will cross a weekend so that people who happen to be gone for the week will have a chance to see it). Everyone interested is invited to comment. BSC members will be called to vote at the end of the discussion.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b>Background: </b><span style="COLOR: black">instructions about when to add or omit spaces are split between 0G4 ("Spacing") and 0G10 (called "Initials, etc." but in fact entirely about spacing of initials and abbreviations). There's a
desire to move them all into 0G4 (which, thankfully, won't cause cascading re-numbering of other rules)</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><b><span style="COLOR: black">Proposal:</span></b><span style="COLOR: black"> Move 0G10 directly into the 0G4 hierarchy, as 0G4.4, with existing headings intact. Note that this will add a decimal sub-level not otherwise seen until 4A6.2.1.
See below for the revised 0G4, using DCRM(B) as the base text, and the mark of omission to help keep this message from getting even longer:
</span></p>
<p class="Header3">0G4. Spacing</p>
<p class="Normalparagraph"><span class="normalbold">0G4.1. Spacing within words and numbers.
</span>In general, follow modern spacing conventions when transcribing from the source....</p>
<p class="Normalparagraph"><span class="normalbold">0G4.2. Spacing between words.
</span>If spacing between words in the source is ambiguous, or lacking, include spaces in the transcription to separate the words as needed...,</p>
<p class="Normalparagraph"><span class="normalbold">0G4.3. Variant spellings.</span> Do not insert spaces within single words that merely represent variant or archaic spellings....</p>
<p class="Header3">0G4.4. Initials, etc.</p>
<p class="Normalparagraph"><span class="normalbold">0G4.4.1. </span>Transcribe initials, initialisms, and acronyms without internal spaces, regardless of how they are presented in the source of information....</p>
<p class="Normalparagraph"><span class="normalbold">0G4.4.2. </span>Treat an abbreviation consisting of more than a single letter as if it were a distinct word, separating it with a space from preceding and succeeding words or initials....</p>
<p class="Normalparagraph"><span class="normalbold">0G4.4.3. </span>If two or more distinct initialisms (or sets of initials), acronyms, or abbreviations appear in juxtaposition, separate them with a space....</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Any discussion?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> Erin. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">--------------------------------------------------<br>
Erin C. Blake, Ph.D. | Curator of Art & Special Collections | Folger Shakespeare Library | 201 E. Capitol St. SE | Washington, DC 20003-1004 | office tel. (202) 675-0323 | fax: (202) 675-0328 | eblake@folger.edu | www.folger.edu | collation.folger.edu</p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>