RE: XML schema interop problems

Don't understand (perhaps strongly disagree with) this one: 

> - discourage/prohibit references to the elements, leaving the 
> references only to the types

Simon Cox 

> -----Original Message-----
> From: xmlschema-dev-request@w3.org 
> [mailto:xmlschema-dev-request@w3.org] On Behalf Of Vladislav Bezrukov
> Sent: Wednesday, 27 April 2005 5:24 PM
> To: xmlschema-dev@w3.org
> Subject: XML schema interop problems
> 
> 
> Hi,
> 
> I am interesting to see the following topics discussed at the 
> User Experiences workshop held on 21-22 June 2005 in Redwood Shores.
> 
>     * interoperability problems
> - presence of minOccurs/maxOccurs on the top-level elements 
> infringing the XML Schema
> - missing empty elements in the XML instances hinders the use 
> of XML Schema
> - presence of additional undeclared elements in the XML 
> instances hinders the use of XML Schema
> 
>     * features missing in XML Schema 1.0?
> - it should be possible to define a behaviour for additional 
> or missing elements that will not invalidate the schema. 
> Current solution is not good enough.
> - healthy concept for versioning and extensions
> - mustIgnore/mustUnderstand rules
> - discourage/prohibit references to the elements, leaving the 
> references only to the types
> 
> regards,
> Vladislav
> 
> Disclaimer: this e-mail represents my personal opinion, I am 
> not speaking on behalf of my employer.
> 
> -- 
> +++ GMX - die erste Adresse für Mail, Message, More +++
> 
> 10 GB Mailbox, 100 FreeSMS  http://www.gmx.net/de/go/topmail
> 
>