OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [relax-ng] attribute constraint

What exactly is the wildcard constraint on attributes that we are 
considering? The issues list says:

"After the simplification, if an <attribute> has <nsName> or <anyName> as 
its name, then its parent must be <oneOrMore>."

Shouldn't this be "ancestor" rather than "parent"?

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

    <attribute name="x"/>
    <attribute name="y"/>
    <attribute name="z"/>

shorthand for a group of optional attributes, which Murata-san suggested at 
some point.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC