<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Arial Unicode MS;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Times;
}
@font-face {
font-family: @Arial Unicode MS;
}
@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
}
P.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt
}
SPAN.MarkeringsbobletekstTegn {
FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.emailstyle17 {
TEXT-TRANSFORM: none; FONT-VARIANT: normal !important; FONT-STYLE: normal; LETTER-SPACING: 0pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: black; VERTICAL-ALIGN: baseline; FONT-WEIGHT: normal; TEXT-DECORATION: none
}
SPAN.markeringsbobleteksttegn0 {
FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.EmailStyle22 {
POSITION: relative; TEXT-TRANSFORM: none; FONT-VARIANT: normal !important; FONT-STYLE: normal; LETTER-SPACING: 0pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: black; VERTICAL-ALIGN: baseline; FONT-WEIGHT: normal; TEXT-DECORATION: none; TOP: 0pt
}
.MsoChpDefault {
FONT-SIZE: 10pt
}
</style><style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" vlink="purple" link="blue" fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Arial Unicode MS;color: #000000;font-size: 12pt;">
<p><font face="Arial">Hi, everyone,<br>
<br>
I'm moving the discussion Axel and I have been having off-line to MEI-L as I think it may be of interest to others.<br>
<br>
Regarding the bibliographic customization posted earlier, Axel said:</font></p>
<p><font face="Arial"></font><br>
<font face="Times New Roman">> I see that <physLoc> is moved out of <physDesc>, but <provenance> is not. Shouldn’t <physLoc> and <provenance> go along?<br>
<br>
[...]<br>
<br>
> I see <provenance> as something like the history of <physLoc>, and as such I would expect their close relationship to be reflected by the schema. It’s a great improvement that <physLoc> is moved out of <physDesc>. But <physLoc> being a sibling of <physDesc>,
while <provenance> is still a child of <physDesc> does not make much sense to me. How about making <provenance> a child of <physLoc> instead? That wouldn’t further increase the number of immediate children of <item>, and it would keep <physLoc> and <provenance>
together in a way that would make sense to me:<br>
<br>
<item><br>
...<br>
<physDesc><br>
...<br>
</physDesc><br>
<physLoc><br>
...<br>
<provenance/><br>
</physLoc><br>
...<br>
</item><br>
</font><br>
<font face="Arial">I agree that <provenance> can be a history of physical location(s), but it doesn't make sense as a child of <physLoc> when multiple <physLoc> elements are allowed, as is the case of <source> or when an <item> has component parts.<br>
<br>
In the following case<br>
<br>
<source><br>
<physDesc/><br>
<physLoc><br>
<repository/><br>
<identifier/><br>
<provenance>...</provenance><br>
</physLoc><br>
<physLoc>...</physLoc><br>
</source><br>
<br>
does the provenance information pertain to only the copy in the first physical location or to both? If it pertains to both, then the <provenance> elemement shouldn't be a child of the first <physLoc>, but should exist outside it. Assuming <provenance> is
permitted only within <physLoc>, if I want to say that both copies have always been kept together, then information will have to be repeated. For example,<br>
<br>
<source><br>
<physDesc/><br>
<physLoc><br>
<provenance>Always together</provenance><br>
</physLoc><br>
<physLoc><br>
<provenance>Always together</provenance><br>
</physLoc><br>
</source><br>
<br>
The same is true for<br>
<br>
<item><br>
<componentGrp><br>
<item><br>
<physLoc><br>
<provenance>...</provenance><br>
</physLoc><br>
</item><br>
<item><br>
<physLoc><br>
<provenance>...</provenance><br>
</physLoc><br>
</item><br>
</componentGrp><br>
</item><br>
<br>
The phrase "exist outside it" above, however, doesn't mean that it has to be a sibling of <physLoc> -- it can reside inside <physDesc>, which is a sibling of <physLoc>. Taking the first case above, <physDesc> can be moved outside either of the <physLoc> elements
so that it can apply to both locations.<br>
<br>
<source><br>
<physDesc><br>
<provenance>...</provenance><br>
</physDesc><br>
<physLoc><br>
<repository/><br>
<identifier/> <br>
</physLoc><br>
<physLoc>...</physLoc><br>
</source><br>
<br>
As part of <physDesc>, <provenance> can be associated with either <source> or <item>. This permits a description of provenance independent of the number of locations. If, however, one item's history is somehow different from its fellows, then this can be
accommodated in the text as well.<br>
<br>
Making <provenance> siblings of <physDesc> and <physLoc> (and probably by extension <exhibHist>, <treatHist>, and <treatSched> as well) instead of children of <physDesc> will break backward compatibility as will allowing them only within <item>, and not <source>.
If they're allowed in both places (that is, in <physDesc> and as siblings of <physDesc>, then that will increase the complexity of the schema and therefore decrease the likelihood it will be used properly. So, I'm inclined to leave well enough alone on this
one.<br>
<br>
Best wishes,<br>
<br>
--<br>
p.<br>
<br>
</font><br>
__________________________<br>
Perry Roland<br>
Music Library<br>
University of Virginia<br>
P. O. Box 400175<br>
Charlottesville, VA 22904<br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu<br>
</p>
</div>
</body>
</html>