Re: Open content model non-deterministic

"Martin Gudgin" <mgudgin@microsoft.com> writes:
> 
> I've been updated the schema for our spec[1] and have run into trouble
> describing out completely open content model. I think we agreed in Paris
> that EIIs from other namespaces could appear absolutely anywhere.
> Unfortunately due to the optional nature of, for example, the import and
> type EIIs this makes the content model for, in this example,
> definitions, non-deterministic. The operation EIIs inside bindings have
> a similar problem.

Ouch, non-determinism is bad.

> If we make things only extensible at the end ( or at the beginning ),
> this problem will go away. For definitions we could allow extension
> elements at any point AFTER import and type...

+1. For consistency sake, should we say that extension elements must
always appear *after* any WSDL 1.2 elements?

Sanjiva.