<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<style type="text/css" id="owaParaStyle"></style><style type="text/css"></style><style type="text/css"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Arial Unicode MS;color: #000000;font-size: 12pt;">
<div><br>
</div>
Hi Zoltan,
<div><br>
</div>
<div>I think the answer to your question lies in the definition of "<span style="font-size: 12pt;">everywhere where it is not impractical". </span><span style="font-size: 12pt;">The adopted strategy is to add the attributes in att.pointing and ptr or ref child
elements when there's a specific need. It would be technically possible to make these attributes (easiest) and child elements (somewhat more difficult) more widely available, but then</span><span style="font-size: 12pt;"> it would be necessary to provide
clear explanations of use of those attributes for every element. That seems to me to be a pretty daunting task. We could, I suppose, in effect say, "use them for whatever purpose you want." But, then their effectiveness for any given purpose is degraded
and processing and interchange capabilities are diminished.</span></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div>Do you have a specific case where you think att.pointing (or ptr/ref) would be a useful addition?</div>
<div><br>
</div>
<div>--</div>
<div>p.</div>
<div>
<div>
<div class="BodyFragment"><font size="2">
<div class="PlainText"><br>
__________________________<br>
Perry Roland<br>
Music Library</div>
<div class="PlainText">University of Virginia</div>
<div class="PlainText">P. O. Box 400175</div>
<div class="PlainText">Charlottesville, VA 22904<br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu</div>
</font></div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF641982" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> mei-l [mei-l-bounces@lists.uni-paderborn.de] on behalf of Kőmíves Zoltán [zolaemil@gmail.com]<br>
<b>Sent:</b> Friday, August 01, 2014 4:58 AM<br>
<b>To:</b> Music Encoding Initiative<br>
<b>Subject:</b> Re: [MEI-L] pointing mechanism<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Thanks Andrew, it looks like this will be the only solution.
<div><br>
</div>
<div>Just out of curiosity back to my alternative question: what is the idea behind ptr/ref, why are they allowed on certain elements and not on others? </div>
<div><br>
</div>
<div>Thanks</div>
<div>Z</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-07-23 20:54 GMT+02:00 Andrew Hankinson <span dir="ltr">
<<a href="mailto:andrew.hankinson@mail.mcgill.ca" target="_blank">andrew.hankinson@mail.mcgill.ca</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div style="word-wrap:break-word">xinclude will essentially create a single serialized XML file from a number of files, so no, you can’t have duplicate IDs.
<div><br>
</div>
<div>One solution we’ve used before is to have automatically-generated UUIDs. They’re a bit cumbersome, but it’s almost impossible to generate two of the same. An XML ID must start with a letter, though, so I generally prefix the UUID with “m-“.</div>
<div><br>
</div>
<div>-Andrew</div>
<div><br>
<div>
<div class="">
<div>On Jul 23, 2014, at 8:45 PM, Kőmíves Zoltán <<a href="mailto:zolaemil@gmail.com" target="_blank">zolaemil@gmail.com</a>> wrote:</div>
<br>
</div>
<blockquote type="cite">
<div class="">
<div dir="ltr">Well yes, it is mainly for practical reasons. One of the practicalities is that if I separate the music content, I don't have to make sure that xml:id across all the musical text are unique. If XInclude can deal with the duplicate ids, then it
sounds like a good solution...
<div><br>
</div>
<div>Z</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div class="">2014-07-23 16:56 GMT+01:00 Raffaele Viglianti <span dir="ltr"><<a href="mailto:raffaeleviglianti@gmail.com" target="_blank">raffaeleviglianti@gmail.com</a>></span>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">Hi Zoltan,
<div>
<div class="h5">
<div><br>
</div>
<div>Why is the musical text contained at another location? What do you need to model? If it's at another location just for practical /architectural reasons, I'd consider using XInclude instead of ptr/ref.</div>
<div><br>
</div>
<div>Raff</div>
</div>
</div>
</div>
<div>
<div class="h5">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>
<div>On Wed, Jul 23, 2014 at 11:36 AM, Kőmíves Zoltán <span dir="ltr"><<a href="mailto:zolaemil@gmail.com" target="_blank">zolaemil@gmail.com</a>></span> wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div>
<div>
<div dir="ltr">Dear MEI-L people!
<div><br>
</div>
<div>I'm trying to express that the musical text is contained at another location, however neither of music, body, mdiv and score elements allow the pointing attributes, nor they can contain ptr of ref elements. I could rely on referencing from a section element,
but I wonder why I cannot do it from higher level ones? </div>
<div><br>
</div>
<div>Or my question worded in another way: the pointing mechanism provided by ptr, ref and the att.pointing attribute class, from their description in the Guidelines, seem to be very generic. I'd assume if it is generic, it would be allowed everywhere where
it is not impractical, but their use seem to be a lot more restricted. Why is that?</div>
<div><br>
</div>
<div>Thanks a lot</div>
<div>Zoltan</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div>
<div class="h5">_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>