<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=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 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
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Markeringsbobletekst Tegn";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.MarkeringsbobletekstTegn
{mso-style-name:"Markeringsbobletekst Tegn";
mso-style-priority:99;
mso-style-link:Markeringsbobletekst;
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Arial","sans-serif";
font-variant:normal !important;
color:black;
text-transform:none;
position:relative;
top:0pt;
mso-text-raise:0pt;
letter-spacing:0pt;
text-shadow:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
font-variant:normal !important;
color:black;
text-transform:none;
position:relative;
top:0pt;
mso-text-raise:0pt;
letter-spacing:0pt;
text-shadow:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
.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"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi Klaus<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I see your point. But if we are talking about the source’s history in more general terms, the <history> perhaps shouldn’t be located inside <physLoc>. Having <history>
inside <physLoc> would suggest something like the archive’s history to me rather than the source’s. Within <physLoc>, I think it should be restricted to actually describe the provenance only and therefore keep the name.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Using a <history> element located outside of <physLoc> to describe provenance, on the other hand, would leave us with the problem we have now (and as in my suggestion
#4, by the way) that it is difficult to tell which history-like elements relate to which <physLoc>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">That doesn’t mean that <history> is out of place in <source>. Especially with printed sources it would make a good place to describe the publishing process, for
instance. <provenance> can only relate to items (even if it is allowed in <source>, if you don’t use FRBR), so having a more general <history> element at source level may be a good idea.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">/axel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Fra:</span></b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Klaus Rettinghaus [mailto:klaus.rettinghaus@gmail.com]
<br>
<b>Sendt:</b> 10. november 2015 13:46<br>
<b>Til:</b> Axel Teich Geertinger<br>
<b>Emne:</b> Re: [mei-catalog-ig] <physLoc> and <provenance><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Hello Perry, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal">this is most likely the move that makes most sense. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">But I was asking myself if <provenance> (as it provides some 'historical' information) tells us only something about the location of a source or more of the source itself? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Personally I would assume the latter. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So why not drop <provenance> completely and replace it with <history> as in <work>. In either place <history> should provide information about events (with persons, dates, and places all along) or more of unstructered data in a simple <p>.
That approach would clear up and simplify some things. Or am I missing something there? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Klaus<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
Am Di, 10. Nov, 2015 um 1:24 schrieb Axel Teich Geertinger <<a href="mailto:atge@kb.dk">atge@kb.dk</a>>:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi Perry</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I agree (I guess that’s why I listed it as no. 1). Furthermore, having <provenance> as a child of <physLoc> would also nicely fit the assumption that the latest
provenance event refers to the source’s current location. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">/axel</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Fra:</span></b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mei-catalog-ig [<a href="mailto:mei-catalog-ig-bounces@lists.uni-paderborn.de">mailto:mei-catalog-ig-bounces@lists.uni-paderborn.de</a>]
<b>På vegne af </b>Roland, Perry D. (pdr4h)<br>
<b>Sendt:</b> 9. november 2015 20:54<br>
<b>Til:</b> <a href="mailto:mei-catalog-ig@lists.uni-paderborn.de">mei-catalog-ig@lists.uni-paderborn.de</a><br>
<b>Emne:</b> Re: [mei-catalog-ig] <physLoc> and <provenance></span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Since <physLoc> can occur more than once within <source> (necessary because <item> isn’t available when MEI.frbr is turned off), it seems to me that the best option is #1. It involves the least amount of change to the content models of
<item> and <source>; that is, only a move of <provenance> from <physDesc> to <physLoc>.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Because it’s a pretty simple change, it’s easy to implement quickly. There’s no fixed deadline for changes to the next release of MEI, but I’d rather make the change sooner than later. While we’re in “metadata revising” mode, I’d also
like to discuss a couple more modifications to the header, but I’ll post separate messages about those soon.<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</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:9.5pt;font-family:"Times New Roman","serif";color:black">
<hr size="3" width="100%" align="center">
</span></div>
<p class="MsoNormal"><b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Fra:</span></b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mei-catalog-ig [<a href="mailto:mei-catalog-ig-bounces@lists.uni-paderborn.de">mailto:mei-catalog-ig-bounces@lists.uni-paderborn.de</a>]
<b>På vegne af </b>Axel Teich Geertinger<br>
<b>Sendt:</b> 2. november 2015 21:19<br>
<b>Til:</b> <a href="mailto:mei-catalog-ig@lists.uni-paderborn.de">mei-catalog-ig@lists.uni-paderborn.de</a><br>
<b>Emne:</b> [mei-catalog-ig] <physLoc> and <provenance></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Dear Metadata IG<br>
<br>
As you know, a new version of the MEI schema is in preparation which will break backwards compatibility in a few instances. I think we should take the opportunity to make a recommendation regarding an issue that has been raised a few times but never resolved.
<br>
In late 2012, the content model of the MEI header was revised. Until then, both <physLoc> (holding information about the physical location of a source) and <provenance> had both been children of the source's <physDesc> (physical description). With the revision,
<physLoc> was moved out of <physDesc> to become its sibling, while <provenance> stayed within <physDesc>.<br>
Please see the discussion from December 2012 below. Since then, the FRBR module has become an optional part of the MEI schema, but that doesn't solve the problem regarding the <provenance> element's place. The issue was brought up again in early April 2014
on MEI-L. You may find it in the archives: <a href="https://lists.uni-paderborn.de/pipermail/mei-l/2014/date.html" target="_blank">
https://lists.uni-paderborn.de/pipermail/mei-l/2014/date.html</a> (look for the 'history of sources / items' discussion).<br>
<br>
My first problem with the current state is that I cannot understand the account of an item's provenance as part of its physical description. Provenance is part of an item's history, and it cannot be described from the item's physical appearance (even if, of
course, the provenance may have left a few physical trails, such as library stamps or written shelf marks).
<br>
The second problem is how to use the current model. When using MEI without the FRBR module, the <item> element is not available and therefore all item-related information must be encoded at source level. That means: if there is more than one copy of a particular
source, all the copies' physical locations and their provenance must be recorded within the same <source> element. But with <physLoc> and <provenance> separated, how can we tell which provenance corresponds to which current location (see the discussion below)?<br>
<br>
There are a number of possible solutions that I can imagine. All of them imply moving <provenance> out of <physDesc>:<br>
1. <provenance> could become a child of <physLoc>. This way, <provenance> would be regarded as supplementary information to the item's current location - or <physLoc>'s historical record, so to speak. Something like this:<br>
<physLoc><br>
<repository/><br>
<identifier/><br>
<provenance><br>
<eventList/><br>
...<br>
</provenance><br>
</physLoc><br>
<br>
2. The other way around: <physLoc> could be a child of <provenance> (which in turn would become a sibling of <physDesc>). This would make <physLoc> more like the end point of a provenance time line:<br>
<provenance><br>
<physLoc><br>
<repository/><br>
<identifier/><br>
</physLoc><br>
<eventList/><br>
...<br>
</provenance><br>
<br>
3. A new container for both could be introduced to group them as siblings (I can't think of a suitable name for such a container, though)
<br>
<br>
4. <provenance> could simply become a sibling of <physLoc> and a direct descendant of <source> (and <item>, of course, when using the FRBR module):<br>
<source><br>
...<br>
<physDesc/><br>
<physLoc><br>
<repository/><br>
<identifier/><br>
</physLoc><br>
<provenance><br>
</eventList/><br>
...<br>
</provenance><br>
...<br>
</source></span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">5. All the solutions I haven't thought of...</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Any opinions? It would be nice to have consensus in this group as much as possible before making any suggestions to MEI-L and filing an issue for the next release.</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Best,</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Axel</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:9.5pt;font-family:"Times New Roman","serif";color:black">
<hr size="3" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Fra:</span></b><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><a href="mailto:mei-l-bounces@lists.uni-paderborn.de"><span lang="DA">mei-l-bounces@lists.uni-paderborn.de</span></a></span><span lang="DA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
[mei-l-bounces@lists.uni-paderborn.de] på vegne af Roland, Perry (pdr4h) [pdr4h@eservices.virginia.edu]<br>
<b>Sendt:</b> 8. december 2012 15:25<br>
<b>Til:</b> Music Encoding Initiative<br>
<b>Emne:</b> Re: [MEI-L] physLoc</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">Axel,</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">To describe the provenance of two copies in different locations, I would leave your example exactly as it is. Or I might even compress the two <provenance> elements into one --</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><source></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <provenance>This relates to one location. This relates to the other location.</provenance></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <repository>some archive</repository></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <repository>some other archive</repository></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"></source></span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">The text in <provenance> explains its relationship to the items in the different locations.</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">@sameas is incorrect, but I would not attempt to connect the <provenance> element to the <physLoc> elements. That's a level of detail that is not required using this "text-based" approach.
Going to the FRBR approach is a better option for that level of detail.</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">In order to make the distinction between the two approaches more clear, it might be worth considering allowing only one <physLoc> in <source>. The example then would be
</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><source></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <provenance>This relates to one location. This relates to the other location.</provenance></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <repository>some archive. some other archive</repository></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"></source></span><span style="font-size:12.0pt;font-family:"Arial Unicode MS","sans-serif";color:black">
</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black"> </span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">--</span><o:p></o:p></p>
<p><span style="font-family:"Arial Unicode MS","sans-serif";color:black">p.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Unicode MS","sans-serif";color:black"><br>
__________________________<br>
Perry Roland<br>
Music Library</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Unicode MS","sans-serif";color:black">University of Virginia</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Unicode MS","sans-serif";color:black">P. O. Box 400175</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Unicode MS","sans-serif";color:black">Charlottesville, VA 22904<br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:9.5pt;font-family:"Times New Roman","serif";color:black">
<hr size="3" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a> [mei-l-bounces@lists.uni-paderborn.de] on behalf of Axel Teich Geertinger [atge@kb.dk]<br>
<b>Sent:</b> Saturday, December 08, 2012 5:59 AM<br>
<b>To:</b> Music Encoding Initiative<br>
<b>Subject:</b> Re: [MEI-L] physLoc</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi Perry,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">to get back to the physLoc question: you wrote</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-family:"Arial","sans-serif";color:black">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></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I see that this would require information to be repeated. However, I think usually the situation would rather be that items in different physical locations (typically
copies kept in different archives) would have different provenance. How would you describe that? You would have something like:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><source></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <provenance>This relates to one location</provenance></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <provenance>This relates to the other location</provenance></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physDesc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <repository>some archive</repository></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> <repository>some other archive</repository></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </physLoc></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"></source></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">With <physLoc> and <provenance> separated, you would have to use IDREFs to clarify which provenance is related to which location (or item), right? Is that better
than repeating information or using someting like @sameas in those (rare, I would say) cases, where several items in _<i>different</i>_ locations (or with different shelf marks) share the same provenance?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Have a nice weekend,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Axel</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
</div>
</body>
</html>