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: Re: Improving 7.3 (was Re: Alternative approach for key/keyref)



> For example, a single grammar can have two patterns as below:
>
> <element name="foo">
>   <list>
>     <keyRef name="k"><data type="short"/></key>
>   </list>
> </element>
>
> and
>
> <element name="foo">
>   <list>
>     <keyRef name="k"><data type="short"/></keyRef>
>     <keyRef name="k"><data type="short"/></keyRef>
>   </list>
> </element>
>
> In my understanding, they do *not* make this schema key-ambiguous.  But do
we really
> need this?  We can even have <choice> or <group> between <list> and
<key>/<keyRef>.

I think disallowing this would make things more complicated not simpler.

James




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


Powered by eList eXpress LLC