[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema directory
{I'm not a member of the CPPA list, so they won't see this :} According to the XML namespace standard [1], The prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace. So the declaration is not required, but it might not be illegal to have it. I suggest *not* putting it, since it would cause folks to look twice and wonder if the prefix is being bound to it's non-default value. And it's easier to point buggy software to the URL that shows them where they're non-compliant. :) Also, according to the same spec [2] Prefixes beginning with the three-letter sequence x, m, l, in any case combination, are reserved for use by XML and XML-related specifications. It's not clear if defining The "xml" prefix to have its official value is allowed. :) > We can either replace the contents of > http://www.oasis-open.org/committees/ebxml-msg/schema/xml-lang.xsd with the > contents of the above file, or we can update our schema and examples to use > the above URL as the schema location. I think it is simpler to do the > former. Again, it would lead to some puzzled looks. I would refer to the official canonical location. /r$ [1] http://www.w3.org/TR/REC-xml-names/#nsc-NSDeclared [2] http://www.w3.org/TR/REC-xml-names/#xmlReserved -- Zolera Systems, Securing web services (XML, SOAP, Signatures, Encryption) http://www.zolera.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC