<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1207178981;
mso-list-type:hybrid;
mso-list-template-ids:262824476 -131936210 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:16;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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"><o:p> </o:p></p>
<p class="MsoNormal">I sent this message to the cataloging interest group list earlier. I apologize if you receive it twice, but I thought it would be a good idea to post to this list as well in the interest of generating as much discussion as possible.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">BTW, this is not a new feature, but rather a remedy for an existing bug. But I think it’s finally squashed this time.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">p.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Roland, Perry D. (pdr4h)
<br>
<b>Sent:</b> Monday, November 09, 2015 3:46 PM<br>
<b>To:</b> 'mei-catalog-ig@lists.uni-paderborn.de'<br>
<b>Subject:</b> changes to <eventList> and <event><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know we’ve had a few rounds of discussion about the content models of <eventList> and <event> in the past. I think there are basically 2 issues currently facing us:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>eventList contains a bug that doesn’t allow grouping events that share the same date<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>the model of event is too vague<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I propose to remedy the first problem by using the following content model for <eventList>:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">eventList (head*, listHead?, (date, (event | eventGrp))*, biblList*)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">By placing <date> outside the model of <event>, the main content of <eventList> can be constrained to be any number of pairs of <date> and <event> elements, like so –<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><eventList><o:p></o:p></p>
<p class="MsoNormal"> <date><!-- when “it” happened --></date><o:p></o:p></p>
<p class="MsoNormal"> <event><!-- what happened --><o:p></o:p></p>
<p class="MsoNormal"> <date><!-- another happening --></date><o:p></o:p></p>
<p class="MsoNormal"> <event><!-- another description --><o:p></o:p></p>
<p class="MsoNormal"><!-- and so on --><o:p></o:p></p>
<p class="MsoNormal"></eventList><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Or, when multiple events share the same date, like so --<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><eventList><o:p></o:p></p>
<p class="MsoNormal"> <date><!-- the date --></date><o:p></o:p></p>
<p class="MsoNormal"> <eventGrp> <!-- the events occurring on the date --><o:p></o:p></p>
<p class="MsoNormal"> <event>Event 1</event><o:p></o:p></p>
<p class="MsoNormal"> <event> Event 2</event><o:p></o:p></p>
<p class="MsoNormal"> <!-- and so on --><o:p></o:p></p>
<p class="MsoNormal"> </eventGrp><o:p></o:p></p>
<p class="MsoNormal"></eventList><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The new model also introduces listHead, a new formatting element. <listHead> contains a pair of <head> elements, one for each column in the eventList date-event pair. This makes it possible to treat the list of events as though it were
a table with a column heading for the dates and a heading for the descriptions. Of course, eventList/head continues to contain a heading for the entire list --<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><eventList><o:p></o:p></p>
<p class="MsoNormal"> <head>My List o’ Special Events</head><o:p></o:p></p>
<p class="MsoNormal"> <listHead><o:p></o:p></p>
<p class="MsoNormal"> <head>When</head><o:p></o:p></p>
<p class="MsoNormal"> <head>What</head><o:p></o:p></p>
<p class="MsoNormal"> </listHead><o:p></o:p></p>
<p class="MsoNormal"> <event/><o:p></o:p></p>
<p class="MsoNormal"> <event/><o:p></o:p></p>
<p class="MsoNormal"></eventList><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I plan to investigate how this might work for other lists as well, such as <biblList>, <castList>, and <list>. Any list that allows a label preceding its “items” could benefit from this treatment, I think.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One more change -- <eventList> is now a member of model.listLike, meaning it can occur not just in the header but anywhere a “regular” list can happen.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The <event> element now has the following model (switching to RNG as it’s somewhat clearer than DTD syntax) --<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><content><o:p></o:p></p>
<p class="MsoNormal"> <rng:optional><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.labelLike"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:optional><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <!-- data-like organization --><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.eventPart"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="eventList"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <!-- free-form organization --><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <!-- model.listLike is expanded here in order to disallow biblList --><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.pLike"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.tableLike"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="castList"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="eventList"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="list"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="biblList"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"></content><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">English translation is “an optional label, followed by EITHER some data-like elements or nested eventLists OR any number of paragraphs, tables, castLists, eventLists, or lists, followed by any number of lists of bibliographic citations.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The central choice (a data-centric organization OR a free-form text one) is the important factor here. In purely practical terms, any file that formerly used a group of data elements followed by a paragraph will have to be translated into
-- <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><event><o:p></o:p></p>
<p class="MsoNormal"> <label><!-- former paragraph content --><o:p></o:p></p>
<p class="MsoNormal"> <geogName/><persName/> <!-- etc. --><o:p></o:p></p>
<p class="MsoNormal"></event><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This element re-naming and re-ordering is not a difficult task and can be made part of the 2013 -> 2015 XSLT transformation. If the re-ordering poses a significant issue (that is, you *<b>must</b>* have the data elements followed by the
label), I think it’s not a problem to allow that, but please let me know.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As always, I apologize for the length of the message and the XML “gobbledy-gook”. I just don’t know of any other way to communicate. ;-)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">p. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">________________________________<br>
Perry Roland<br>
University of Virginia<br>
</span>P. O. Box 400874<o:p></o:p></p>
<p class="MsoNormal">Charlottesville, VA, 22904<span style="color:black"><br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>