[MEI-L] <syl> inside <choice>
Roland, Perry (pdr4h)
pdr4h at eservices.virginia.edu
Thu Mar 8 20:57:40 CET 2012
Hi, Thomas,
I just validated your examples against /trunk/schemata/mei-all.rng, which I believe reflects the proper behavior expressed in the current version of mei-source.
Because <choice> is a member of model.editLike, it is allowed in the content of <syl>.
<!-- syl content -->
<content>
<rng:zeroOrMore>
<rng:choice>
<rng:text/>
<rng:ref name="model.textphraseLike.limited"/>
<rng:ref name="model.editLike"/>
<rng:ref name="model.transcriptionLike"/>
</rng:choice>
</rng:zeroOrMore>
</content>
So, this should validate:
<syl>
<choice>
<orig><!-- English --></orig>
<reg><!-- German --></orig>
</choice>
</syl>
The following is (perhaps unfortuntely) also permitted
<syl>
<orig/>
<reg/>
</syl>
because <syl> also allows model.transcriptionLike members, one of which is <orig>, as do many elements that allow mixed content.
In this case, no choice between the 2 things is suggested. The assumption is that the members of transcriptionLike, most usefully <add>, <del>, <sic>, <corr>, etc., will be used to mark parts of the text phrase, as in
<syl>glare<add>d</add></syl>
which indicates that the 'd' was added later.
The <orig> and <reg> elements come as part of the transcriptionLike class -- it's too hard to exclude them.
The <syl> element is *not allowed* in any of the transcriptionLike elements, such as <orig> or <reg> because
<choice>
<orig>
<syl>Ms.</syl>
</orig>
<reg>
<syl>Miss</syl>
</reg>
</choice>
can be expressed more succinctly as
<syl>
<choice>
<orig>Ms.</orig>
<reg>Miss</reg>
</choice>
</syl>
and, unlike some other things under discussion recently, in this case the decision was to allow only one way to do it. (MEI, like most other things in the real world, is not completely self-consistent -- sue me.)
Unless the customization service is using an outdated/cached version of mei-source.xml, I can't say why you're getting different behavior. Maybe this is a question for Daniel R.
Hope this helps,
--
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-bounces at lists.uni-paderborn.de [mei-l-bounces at lists.uni-paderborn.de] on behalf of TW [zupftom at googlemail.com]
Sent: Thursday, March 08, 2012 12:10 PM
To: Music Encoding Initiative
Subject: Re: [MEI-L] <syl> inside <choice>
It seems the following is legal:
<?xml version="1.0" encoding="UTF-8"?>
<mei xmlns="http://www.music-encoding.org/ns/mei">
<meiHead>
<fileDesc>
<titleStmt>
<title/>
</titleStmt>
<pubStmt/>
</fileDesc>
</meiHead>
<music>
<body>
<mdiv>
<score>
<section>
<measure>
<staff>
<layer>
<note>
<syl>
<orig>Ms.</orig>
<reg>Miss</reg>
</syl>
</note>
</layer>
</staff>
</measure>
</section>
</score>
</mdiv>
</body>
</music>
</mei>
But why like this and not with <choice>?
Thomas
2012/3/8 TW <zupftom at googlemail.com>:
> I just tried something like:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <mei xmlns="http://www.music-encoding.org/ns/mei">
> <meiHead>
> <fileDesc>
> <titleStmt>
> <title/>
> </titleStmt>
> <pubStmt/>
> </fileDesc>
> </meiHead>
> <music>
> <body>
> <mdiv>
> <score>
> <section>
> <measure>
> <staff>
> <layer>
> <note>
> <choice>
> <orig>
> <syl>Ms.</syl>
> </orig>
> <reg>
> <syl>Miss</syl>
> </reg>
> </choice>
> </note>
> </layer>
> </staff>
> </measure>
> </section>
> </score>
> </mdiv>
> </body>
> </music>
> </mei>
>
>
> I let oXygen validate against the RNG that the web service gave me,
> and it complains about <syl> in <orig> or <reg>. Indeed, the
> documentation says, <syl> is only allowed inside <lem>, <rdg>,
> <verse>, <syllable> and <note>. Why is this so? Bug or feature?
>
> Thomas
_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de
https://lists.uni-paderborn.de/mailman/listinfo/mei-l
More information about the mei-l
mailing list