[
Lists Home |
Date Index |
Thread Index
]
You could, of course, simply declare the "tag" element mandatory, and
the others optional - but I believe you're looking for a more
"controlled" structure than that (i.e. regarding the sets of elements
that follow "tag"). You could use substitution groups by declaring the
"tag" element mandatory and then following it with a more "general"
element (the head element) that acts as a placeholder - but this would
only work for substituting individual elements, not sets of elements.
Best bet is to define an abstract type for the "modify" content model
with the "tag" element declared as mandatory, and non-abstract types
that derive from the abstract that extend it with the sets of elements
that follow the "tag" element in each required case.
Hope that helps.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Strategy and Technology Consultants to the World
"James, David" wrote:
>
> Joe
>
> > What error message are you getting? (I'm thinking the issue might be
> > non-determinism)
>
> I am trying to define an element as
>
> <xsd:element name="modify">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element ref="tag"/>
> <xsd:all minOccurs="0">
> <xsd:element ref="lowscale"/>
> </xsd:all>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
> and xsv is telling me that 'all' is not allowed at that point. This is
> consistent with the primer saying that 'all' can only exist at the top level
> but I can't see how to specify that the element "tag" is always first,
> followed by one or more elements such as "lowscale" (for simplicity the only
> one that I have included).
>
> Regards,
> David
>
> ------------------------------------------------------------------------
>
> Part 1.2 Type: application/ms-tnef
> Encoding: base64
--
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton
|
