> > 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.
Wow, I didn't know that. I thought it would be OK as long as the content
model is deterministic. But I wonder how that "same name, same type"
restriction makes sense when you can legally write something like:
<sequence>
<element name="foo" type="..."/>
<any namespace="#all" ... />
</sequence>
Or is this invalid, too?
Well, whatever. As TimBL said, "the sucker's been finalized and blessed
and shipped and we're stuck with it."
regards,
--
Kohsuke KAWAGUCHI +1 650 786 0721
Sun Microsystems [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
