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

Unique Particle Attribution question

From: Kriegesmann, Peter <Peter.Kriegesmann@softwareag.com>
Date: Thu, 28 Mar 2002 16:02:49 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E62106023722EE@daemsg02.software-ag.de>
To: xmlschema-dev@w3.org
Dear friends of the XML Schema,

Today I have another question about unique particle attribution as a result
of a discussion within our group.

Take a look at the following schema:

<?xml version = "1.0" encoding = "UTF-8"?>
<xs:schema xmlns:xs = "http://www.w3.org/2001/XMLSchema">
  <xs:element name = "rabbit">
    <xs:complexType>
      <xs:sequence minOccurs = "0" maxOccurs = "unbounded">
        <xs:element name = "egg" type = "xs:string"></xs:element>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

and the corresponding xml document:

<rabbit>
	<egg/>
	<egg/>
</rabbit>

My question:

Does the schema violate against the "Unique particle attribution" [1] ?. 

My colleague says yes, because it cannot be determined, if the 2
"egg"-elements are a product of 1 or 2 sequence-elements and so the part of
the unique particle attribution [1]("each item in the sequence in turn can
be uniquely determined") is not fulfilled.
In my opinion and according to [2] (which does not claim to be complete)  I
do not see a violation, because there is no "overlap" and each item can be
uniquely determined, as there is only one matching element definition
(element-definition of "egg").

The XML document also passes IBM Schema Quality Checker without warnings or
errors.

Your help and opinion is welcome.

Best regards,

Peter

[1] http://www.w3.org/TR/xmlschema-1/#coss-modelGroup
[2] http://www.w3.org/TR/xmlschema-1/#non-ambig


Peter Kriegesmann
Phone	 06151-921484
Electronic Business Technologies (QE)				Fax
06151-921612
			
Software AG
http://www.softwareag.com
Uhlandstrasse 12				
D-64297 Darmstadt
mailto:Peter.Kriegesmann@softwareag.com	
Received on Thursday, 28 March 2002 10:03:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:30 GMT