> +1 for a normative schema .. however that's not impossible while > supporting XML 1.1; that's what WSDL 2.0 is going to be doing. FWIW, I think WSDL 2.0 is horrible; I'll have a column on webservices.xml.com in a day or two that explains it in more detail. I think that if this WG wants to address XML1.1 -- perhaps someone should open a new issue on that exact point -- then it should be in a separate small section at the end of the document. Personally, I see absolutely nothing wrong with saying something like this: XSD does not yet support XML 1.1. XML 1.1 is not fully backward-compatible with XML1.0, nor is it generally available or deployed. Given this, whenever we find ourselves having to choose between support, or clean and simple use of XML1.0/XSD over XML1.1, we chose the former. Section X.Y defines a normative mapping of this specification to XML 1.1. Then we only need someone to volunteer to write the mapping. /r$ -- Rich Salz Chief Security Architect DataPower Technology http://www.datapower.com XS40 XML Security Gateway http://www.datapower.com/products/xs40.html XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.htmlReceived on Saturday, 13 November 2004 13:48:35 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT