<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">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>On Jul 23, 2014, at 8:45 PM, Kőmíves Zoltán <<a href="mailto:zolaemil@gmail.com">zolaemil@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><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 class="gmail_extra"><br><br><div class="gmail_quote">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>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Zoltan,<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 class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">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 class="h5"><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">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>mei-l mailing list<br><a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>https://lists.uni-paderborn.de/mailman/listinfo/mei-l<br></blockquote></div><br></div></body></html>