[MEI-L] <projectDesc>...</projectDesc> and some other elements...

Wed Dec 18 21:55:38 CET 2013

Hi Sigfrid,

The <projectDesc> element does allow "a bit of structure"; that is, it allows a text organized as an ordered set of paragraphs.  It's designed that way because anything more complex probably belongs in music/front or music/back instead.  The same philosophy applies in the case of the other elements that share this model.

It's true that <projectDesc> does not allow <head>, but it does permit @label, which is sufficient unless your heading contains presentational markup, such as sub- or superscripts, font changes, etc.  I'm not opposed to allowing <head> within <projectDesc> -- I'd just ask that you create a ticket in the tracker (https://code.google.com/p/music-encoding/issues) to remind me of this issue for the next release.

Best wishes,

--
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+pdr4h=virginia.edu at lists.uni-paderborn.de] on behalf of Sigfrid Lundberg [slu at kb.dk]
Sent: Wednesday, December 18, 2013 7:16 AM
To: Music Encoding Initiative
Subject: [MEI-L] <projectDesc>...</projectDesc> and some other elements...

<projectDesc>...</projectDesc> and many other elements have (it is just that projectDesc is an issue for one of our projects today) allow textual content within <p>...</p>. However it does not allow <div>...</div> though, and in particular it does not allow <head>...</head>. Why is that?

And what is the best solution if my text is long enough to benefit from a bit of a structure?

Yours

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