<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Californian FB";
panose-1:2 7 4 3 6 8 11 3 2 4;}
@font-face
{font-family:Papyrus;
panose-1:3 7 5 2 6 5 2 3 2 5;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hello, everyone,<o:p></o:p></p>
<p class="MsoNormal"> Attached you will find discussion of an issue that I brought up at the BSC June 22 meeting in Anaheim. As I say at the beginning of it, it has 3 parts: 1) existing or draft rule texts to aid in discussion (these will also sometimes
have yellow highlights, so you will know those are not the actual proposed texts); 2) discussion and 3) at the very end, a summary of the actual proposed texts. These last will be obvious, because I have “simulated” a tracked-changes document by using red
font for the proposed changes. <o:p></o:p></p>
<p class="MsoNormal"> The proposal goes so far as to suggest rule number changes at the end of Area 4 (with reasons given in the discussion portion), but I know that this is a bigger issue than most of us would like to touch, so I am very open to suggestion
of other ways to approach the rule numbering in that section, without removing the added text in that area, which I think is crucial (and hope you agree).<o:p></o:p></p>
<p class="MsoNormal"> I would also suggest that, despite my attempts to help the reading by including existing DCRM(B) text, people would benefit by looking at DCRM(B) and even glancing at AACR2 (when prompted in the discussion) while reading.<o:p></o:p></p>
<p class="MsoNormal"> I am interested in everyone’s comments about this issue, and hope that the DCRM editors will lend their experience with these rule issues to the discussion.<o:p></o:p></p>
<p class="MsoNormal"> --Jain<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"Californian FB","serif";color:#403152">Jain Fletcher<br>
Principal Cataloger & Head, Cataloging Section<br>
Collection Management Division <br>
Library Special Collections<br>
Young Research Library - UCLA Box 951575<br>
Los Angeles, CA 90095-1575<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"Californian FB","serif";color:#403152">v: (310) 794-4096<br>
f: (310) 206-1864<br>
e: </span><span style="font-size:10.0pt;font-family:"Californian FB","serif";color:#403152"><a href="mailto:jfletchr@library.ucla.edu" title="mailto:jfletchr@library.ucla.edu"><span style="font-size:12.0pt;color:#403152">jfletchr@library.ucla.edu</span></a></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal" align="center" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;text-align:center">
<span style="font-size:10.0pt;color:blue">..-.:~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:.-.</span><span style="font-size:12.0pt;font-family:"Californian FB","serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" align="center" style="margin-bottom:12.0pt;text-align:center">
<b><span style="font-family:Papyrus;color:#7030A0">Pedantry and mastery are opposite attitudes toward rules.
<br>
To apply a rule to the letter, rigidly, unquestioningly, in cases where it fits and in cases where it does not fit, is pedantry...
<br>
To apply a rule with natural ease, with judgment, noticing the cases where it fits, and without ever letting the words of the rule obscure the purpose of the action or the opportunities of the situation, is mastery.
<o:p></o:p></span></b></p>
<p class="MsoNormal" align="center" style="margin-bottom:12.0pt;text-align:center">
<b><span style="font-family:Papyrus;color:#7030A0">George Polya, professor of mathematics (1887-1985)<o:p></o:p></span></b></p>
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;color:blue">.-~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:._,_.:~*~:..</span><span style="font-family:"Californian FB","serif""><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>