Re: Question on XSD elements in groups

Hello again, I answered your previous message and maybe it will help, there
is indeed an ambiguity for xml schema between your elements because they are
all declared globaly and xml schema does not know wether or not they can
appear more than once, or so I believe.

Whichever the reason, an easy fix would be to use, in this particular case,
local element declarations, for all said elements in your <xsd:choice> or at
least for either :
the two Symkey and SymkeyErreor element or
the element containing SymkeyWithSymkeyErrorGroup group

Hope it helps.

2008/6/22 Arshad Noor <arshad.noor@strongauth.com>:

>
> 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.
>
>
>
>
>
>