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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Accepting non-deterministic content models

Hi Folks,

The following element, test, has a non-deterministic content model:

<xsd:element name="test">
            <xsd:element name="a" type="xsd:string"/>
            <xsd:element name="b" type="xsd:string"/>
               <xsd:element name="a" type="xsd:string"/>
               <xsd:element name="b" type="xsd:string"/> 

XML Spy 4.0b, xerces 1.4.1 both accept this as valid.

xsv, turbo XML 2.2, and the IBM SQL all generate an error, indicating
that the element, test, has a non-deterministic content model.

Isn't this a bad thing - some parsers accepting non-deterministic
content models, while other parsers rejecting it?

I believe that the origin of this "problem" is that in the XML spec it
states that parsers *should* reject non-deterministic content models.  I
am wondering if perhaps "should" would be better replaced with "must"?