[MEI-L] pointing mechanism

[Roland, Perry D. (pdr4h)]

Hi Zoltan,

I think the answer to your question lies in the definition of "everywhere where it is not impractical".  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 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.

Do you have a specific case where you think att.pointing (or ptr/ref) would be a useful addition?

--
p.

__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h (at) virginia (dot) edu
________________________________
From: mei-l [mei-l-bounces at lists.uni-paderborn.de] on behalf of Kőmíves Zoltán [zolaemil at gmail.com]
Sent: Friday, August 01, 2014 4:58 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] pointing mechanism

Thanks Andrew, it looks like this will be the only solution.

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?

Thanks
Z


2014-07-23 20:54 GMT+02:00 Andrew Hankinson <andrew.hankinson at mail.mcgill.ca<mailto:andrew.hankinson at mail.mcgill.ca>>:
xinclude will essentially create a single serialized XML file from a number of files, so no, you can’t have duplicate IDs.

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-“.

-Andrew

On Jul 23, 2014, at 8:45 PM, Kőmíves Zoltán <zolaemil at gmail.com<mailto:zolaemil at gmail.com>> wrote:

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...

Z


2014-07-23 16:56 GMT+01:00 Raffaele Viglianti <raffaeleviglianti at gmail.com<mailto:raffaeleviglianti at gmail.com>>:
Hi Zoltan,

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.

Raff


On Wed, Jul 23, 2014 at 11:36 AM, Kőmíves Zoltán <zolaemil at gmail.com<mailto:zolaemil at gmail.com>> wrote:
Dear MEI-L people!

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?

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?

Thanks a lot
Zoltan




_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de<mailto:mei-l at lists.uni-paderborn.de>
https://lists.uni-paderborn.de/mailman/listinfo/mei-l



_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de<mailto:mei-l at lists.uni-paderborn.de>
https://lists.uni-paderborn.de/mailman/listinfo/mei-l


_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de<mailto:mei-l at lists.uni-paderborn.de>
https://lists.uni-paderborn.de/mailman/listinfo/mei-l


_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de<mailto:mei-l at lists.uni-paderborn.de>
https://lists.uni-paderborn.de/mailman/listinfo/mei-l


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20140801/a2498497/attachment.html>