[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Relationship among our data model, patterns, and XML 1.0
> But my concern is, what happens if the following pattern is given? > > <oneOrMore> > <choice> > <attribute> > <nsName ns="foo"/> > </attribute> > <attribute name="bar:xyz"/> > </choice> > </oneOrMore> > > Is this still OK? Which aspect of the pattern concerns you? Is it the <choice> inside the <oneOrMore>, or the fact that you have an attribute with a non-infinite class inside <oneOrMore>? I don't think either of these need to be prohibited: the <oneOrMore> has a non-colliding semantics for all attributes. James
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC