- From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
- Date: Wed, 11 Apr 2012 20:52:04 -0600
- To: Frank Meisschaert <Frank.Meisschaert@UGent.be>
- Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, www-xml-schema-comments <www-xml-schema-comments@w3.org>, Liam Quin <liam@w3.org>
On Apr 11, 2012, at 11:25 AM, Frank Meisschaert wrote: > Hello, > > The file http://www.w3.org/2001/XMLSchema.xsd imports the xml.xsd schema with > > <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"> > > However the xml.xsd has been moved to http://www.w3.org/2001/03/xml.xsd The first address is working for me. W3C makes it a practice not to change the URIs of published documents, partly to avoid precisely the kind of problem that arises when URIs do change. See "Cool URIs don't change" (http://www.w3.org/Provider/Style/URI.html) for more on the background to this policy. > Tools like xmllint which import the url directly fail on this. Fortunately, xmllint does come with support for catalogs built in, so you ought to be able to make it read a local copy of the schema document for the XML namespace (and indeed of the XSD schema for XSD schema documents) instead of the one served (very slowly nowadays) by w3.org. I see that Liam Quin has already recommended this. The W3C systems blog post at http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ explains why the W3C server imposes rate limitations on requests for schema documents. I hope this helps. -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net ****************************************************************
Received on Thursday, 12 April 2012 02:52:31 UTC