← Prev in month ← Prev in thread

[relax-ng] attribute constraint

From
James Clark <>
Date
2001-10-15T11:50:33+00:00
ID
6802872.1003171717@[192.168.0.224]
Thread
[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
← Prev in month ← Prev in thread