W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2004

Re: request to specify schema location explicitly for http://www.w3.org/XML/1998/namespace

From: Pete Hendry <peter.hendry@capeclear.com>
Date: Wed, 14 Apr 2004 17:56:48 +1200
Message-ID: <407CD2A0.90708@capeclear.com>
To: Rich Salz <rsalz@datapower.com>
Cc: David Bernstein <dbbernstein@earthlink.net>, "xml-dist-app@w3.org" <xml-dist-app@w3.org>, Yves Lafon <ylafon@w3.org>


Although tools should know about it, it is more interoperable to specify 
schemaLocation. This is only a hint and tools that already have this 
schema locally are free to use the local copy and not go to w3.org for 
it. Tools that don't have it can go get it. With it tools work either 
way, without it tools that don't know about it fail. I would prefer the 
scenario where everything works.

Of course, tools should fall back to resolving the namespace to a 
location to see if that holds the schema, but obviously some don't.


Rich Salz wrote:

>><import namespace="http://www.w3.org/XML/1998/namespace"
>>        schemaLocation="http://www.w3.org/2001/xml.xsd"/>
>I think it is wrong, and non-scaleable, for every potential
>schema-validation to go to the W3C web site for a schema that they should
>all "know" about, anyway.
>The current "trick" (it's legal, so it's not really a trick), of leaving
>off the schemaLocation attribute is doing the right thing.
>It's unfortunate the tools stink.
>	/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.html
Received on Wednesday, 14 April 2004 02:57:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:25 UTC