[tei-council] content model for <attDef>
Sebastian Rahtz
sebastian.rahtz at oucs.ox.ac.uk
Sat Apr 28 14:41:29 EDT 2012
we currently say that an attribute looks like this:
<content>
<group xmlns="http://relaxng.org/ns/structure/1.0">
<zeroOrMore>
<ref name="model.glossLike"/>
</zeroOrMore>
<optional>
<ref name="datatype"/>
</optional>
<zeroOrMore>
<ref name="constraintSpec"/>
</zeroOrMore>
<optional>
<ref name="defaultVal"/>
</optional>
<optional>
<choice>
<ref name="valList"/>
<oneOrMore>
<ref name="valDesc"/>
</oneOrMore>
</choice>
</optional>
<zeroOrMore>
<ref name="exemplum"/>
</zeroOrMore>
<zeroOrMore>
<ref name="remarks"/>
</zeroOrMore>
</group>
</content>
which means that it can end up with no datatype of valList at all.
What do folks think of adding a constraint that, unless its in @mode='change', you must
either supply a closed valList or a datatype?
Sebastian
More information about the tei-council
mailing list