Hi.
> Would you tell me whether you are planning to use (1) the current
> content model or (2) the current state in the current content model?
> This distinction is important for me.
>
> My guess is that you have to use the current state, because sometimes
> the content model by itself is not enough to decide the content model
> for children.
Yes. We need the current state of the current content model to determine
the matching declaration of given child element.
> <xs:complexType name="crap">
> <xs:sequence>
> <xs:element name="foo" type="aType"/>
> <xs:element name="foo" type="anotherType"/>
> </xs:sequence>
> </xs:complexType>
>
> I'm not confident but I guess the above one is a valid XML Schema. To
> decide the type of the content model, you need to see the current state.
This is in fact invalid. In one content model, elements with the same name
must have the same global type. So this is not the reason that we need the
current state. Our reason is to tell whether a given child element matches
an element or a wildcard, and which wildcard.
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-416) 448-3255
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
