[MEI-L] [mei-devel] Attribute default values

Thomas Weber zupftom at web.de
Sat Jun 22 14:59:29 CEST 2013

Am 22.06.2013 14:41, schrieb Zoltan Komives:
> However, in some cases an assumption of a default value can be implied
> by the presence of the explicit information within the same (or nested,
> or nesting) structure.
> E.g. by
> <staffGrp id="outer">
>    <staffGrp id="inner" barthru="true"/>
>    <staffDef/>
>    <staffDef/>
> </staffGrp>

I must agree!

> Do I understand it right, that profiles are meant to handle these sorts
> of ambiguities of encoding? It would be great if you could point me
> towards further info regarding profiles.

My understanding of these ideas is to create subsets of MEI with 
stricter rules that are required to provide more information in a more 
consistent way.  (I'm thinking about something similar to the Open Score 
Format, which is a stricter MusicXML.)  I'm not sure whether anyone has 
already done work on something like this, but I think *ideally* such 
profiles (or however you might call them) should not allow ambiguity to 
start with rather than giving you rules how to resolve ambiguity.

Others might be more competent than me talking about this.


More information about the mei-l mailing list