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]

Re: Accepting non-deterministic content models

I made a dtd for this and tried it out.  Architag XRay and XML Cooktop both
liked it, rxp in validating mode rejected it as non-deterministic but
accepted it when not validating, xmlproc and the validating version of
xmlproc both accepted it.

Here's the test file:

<!DOCTYPE doc [
<!ELEMENT doc (a|b|(a,b))>


Tom P

[Roger L. Costello]

> The following element, test, has a non-deterministic content model:
> <xsd:element name="test">
>     <xsd:complexType>
>         <xsd:choice>
>             <xsd:element name="a" type="xsd:string"/>
>             <xsd:element name="b" type="xsd:string"/>
>             <xsd:sequence>
>                <xsd:element name="a" type="xsd:string"/>
>                <xsd:element name="b" type="xsd:string"/>
>             </xsd:sequence>
>         </xsd:choice>
>     </xsd:complexType>
> </xsd:element>
> 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.