[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [relax-ng] attribute constraint
>
>There's a related possible restriction, which is what I thought Murata-san
>was proposing: if an <attribute> occurs in a <oneOrMore>, then its first
>child must be <nsName> or <anyName>. That would have the disadvantage of
>disallowing the
Actually, in Hosoya-san's normalization, <attribute> is always normalized to <attribute>
within <oneOrMore>. For example,
<element name="foo">
<attribute name="bar"><text/></attribute>
</element>
is normalized into
<element name="foo">
<oneOrMore>
<attribute name="bar"><text/></attribute>
</oneOrMore>
</element>
It is this normalization that makes subsumption checking possible.
Cheers,
Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC