W3C home > Mailing lists > Public > xmlschema-dev@w3.org > November 2002

RE: deterministic or ambiguous?

From: Asir S Vedamuthu <asirv@webmethods.com>
Date: Wed, 6 Nov 2002 08:33:41 -0500
To: "Nell Golding" <nell_golding@hotmail.com>, <xmlschema-dev@w3.org>
Message-ID: <OKEBJFDOCNPMPLOONLOIMELHDDAA.asirv@webmethods.com>

Non-deterministic per XML 1.0, http://www.w3.org/TR/REC-xml#determinism

'cos, you content model in DTD syntax is ((Ack_Nack, Reason_Nack) |
(Ack_Nack, Reason_Nack)).

And, 'Reason_Nack' element decls within the content model must be of the
same type.


-----Original Message-----
From: xmlschema-dev-request@w3.org
[mailto:xmlschema-dev-request@w3.org]On Behalf Of Nell Golding
Sent: Wednesday, November 06, 2002 5:49 AM
To: xmlschema-dev@w3.org
Subject: deterministic or ambiguous?


I have created a XML schema and a sample XML document. According to XMLSpy
4.4 the document seems to be valid and XML schema compliant to the W3C

All other Tools (Topologi Schematron and Markup Editor, XML Schema Validator
from Microsoft) that I used for validation reply that my schema is not
deterministic. They report that there are multiple definitions of some
element that cause content model to be ambiguous.

I woud like to know, whether I make mistakes in schema definition and XMLSpy
doesn't notice them, or these are bugs of the other tools.

Here is a part of my schema that causes difficulties:

<xs:element name="root">
	    <xs:element name="Ack_Nack" type="xs:string" fixed="ACK">
	    <xs:element name="Reason_Nack" type="leer"/>
	    <xs:element name="Ack_Nack" type="xs:string" fixed="NACK">
	    <xs:element name="Reason _Nack" type="Explanation_of_Nack"
                  <xs:documentation>Explanation to the rejection of the

Nill Golding.

Add photos to your e-mail with MSN 8. Get 2 months FREE*.
Received on Wednesday, 6 November 2002 08:31:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:58 UTC