Re: [relax-ng] attribute constraint

[James Clark <jjc@jclark.com>]

The formulation of the restriction also needs to deal with the possibility
that an <attribute> may have a <choice> of <nsName> or <anyName>.  So I
would phrase the restriction as:

After simplification, an <attribute> element that has an <nsName> or
<anyName> descendant element must have a <oneOrMore> ancestor element.

----- Original Message -----
From: "James Clark" <jjc@jclark.com>
To: <relax-ng@lists.oasis-open.org>
Sent: Monday, October 15, 2001 6:48 PM
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
>
> <zeroOrMore>
>   <choice>
>     <attribute name="x"/>
>     <attribute name="y"/>
>     <attribute name="z"/>
>     ...
>   </choice>
> </zeroOrMore>
>
> shorthand for a group of optional attributes, which Murata-san suggested
at
> some point.
>
> James
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>
>