Even though the two particles referring to ekmi:Symkey are effectively
identical, the rules are that an instance element must be attributable to
one of the particles unambiguously.

The solution is to use the content model (a b? | b) in place of (a | b | ab)

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: xmlschema-dev-request@w... 
> [mailto:xmlschema-dev-request@w...] On Behalf Of Arshad Noor
> Sent: 22 June 2008 00:36
> To: xmlschema-dev@w...
> Subject: Question on XSD elements in groups
> 
> 
> I have the following defined in an XSD:
> 
> 
> <xsd:element name="Symkey" type="ekmi:SymkeyType"/> 
> <xsd:element name="SymkeyError" type="ekmi:SymkeyErrorType"/>
> 
> <xsd:group name="SymkeyWithSymkeyErrorGroup">
>      <xsd:sequence>
>         <xsd:element ref="ekmi:Symkey"/>
>         <xsd:element ref="ekmi:SymkeyError"/>
>      </xsd:sequence>
> </xsd:group>
> 
> 
> I'm trying to define a complex type that has a choice of 
> either the Symkey or the SymkeyError elements, or the 
> above-defined group which includes both elements.
> 
> However, the tool I'm using to build the schema keeps giving 
> me the following error:
> 
> Error: cos-nonambig: "http://docs.oasis-open.org/ekmi/2008/01":Symkey
> and "http://docs.oasis-open.org/ekmi/2008/01":Symkey (or 
> elements from their substitution group) violate "Unique 
> Particle Attribution". During validation against this schema, 
> ambiguity would be created for those two particles.
> 
> Since I can only have a Symkey, SymkeyError or a combination 
> of both in the to-be-defined element, why does NB think there 
> will be ambiguity?  How do I go about accomplishing what I 
> want?  Thanks in advance.
> 
> Arshad Noor
> StrongAuth, Inc.
> 
> 
> 
> 
> 


From lists@f... Mon Jun 23 09:31:04 2008
Received: from [128.30.52.63] (helo=bart.w3.org)
	by