[MEI-L] StaffGrp

[Roland, Perry (pdr4h)]

Sorry, I meant to say that I *have not* checked the sample collection thoroughly for this issue.



Johannes is correct -- we have the power to change the examples when they don't match the guidelines.  But I'm also not certain that the guidelines are perfectly clear about this issue since they were developed along with the examples.  Never fear, though -- we have the power to change the guidelines as well!  :-)



--

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 Roland, Perry (pdr4h) [pdr4h at eservices.virginia.edu]
Sent: Tuesday, December 10, 2013 9:21 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] StaffGrp


Hi Laurent,



The outermost staffGrp functions as a kind of "root element" for the set of staffGrp definitions.  Only it, not the inner ones, should have the @symbol="line" attribute -- this controls whether the score has a line at the left edge of the staves or not.  The "inner" staffGrp elements then use @symbol to indicate how the group's staves are connected.



With this in mind, *without the outer group, as in the Ahle example, no line should be drawn.*  There appears, ahem, to be a coding error in the MEI file.  :-)  It's a mistake repeated in nearly all the examples for solo keyboard and maybe (I have checked thoroughly) in those for solo voice and keyboard accompaniment.



I think there's no easy way to prevent this error, since staffGrp is used for both the outer container and the contained groups.  A simple thing that might help would be to create a schematron rule that restricts @symbol="line" to the outer group only.  This way, if one were concerned about the connecting line, the only way to get it would be to properly nest the staffGrp elements.



Does this help?



--

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 Andrew Hankinson [andrew.hankinson at mail.mcgill.ca]
Sent: Tuesday, December 10, 2013 8:45 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] StaffGrp

Hi Laurent,

If you have an inner group with @symbol=line and an outer one with @symbol=brace it’s pretty unambiguous. Are you thinking braceWithLine just to eliminate one level of hierarchy?

-Andrew

On Dec 10, 2013, at 8:25 AM, Laurent Pugin <lxpugin at gmail.com<mailto:lxpugin at gmail.com>> wrote:

Hi,

I have question regarding the @symbol in staffGrp with the value "brace" (or "bracket"). Does it implies a line to be rendered as well or not?

In the examples given in the documentation, most cases with a brace containing all staves, there is usually one single staffGrp (with symbol="brace"), whereas with orchestral score, we usually have one staffGrp with symbol="line" and then sub staffGrps with symbol="brace".

http://www.music-encoding.org/sampleCollection/encodings/Ahle_Jesu_meines_Herzens_Freud.pdf
http://www.music-encoding.org/sampleCollection/encodings/Ahle_Jesu_meines_Herzens_Freud.xml

http://www.music-encoding.org/sampleCollection/encodings/Hummel_Concerto_for_trumpet.pdf
http://www.music-encoding.org/sampleCollection/encodings/Hummel_Concerto_for_trumpet.xml

How can we clarify this? Should we allow something like "braceWithLine" as possible value?

Best,
Laurent
_______________________________________________
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/20131210/661e4e07/attachment.html>