- From: Daniel Veillard <veillard@redhat.com>
- Date: Mon, 4 Mar 2013 23:58:01 +0800
- To: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>
- Cc: "<j-durand@cosoluce.fr>" <j-durand@cosoluce.fr>, bernard.odier@inria.fr, cyan@cosoluce.fr, xmlschema-dev@w3.org, w3c-france@w3.org
On Mon, Mar 04, 2013 at 08:18:18AM -0700, C. M. Sperberg-McQueen wrote: [...] > There are several measures you, or any software developer or user affected by > these issues can undertake. > > - You can and should set up and use some mechanism to allow the schema documents > in question to be retrieved without hitting the W3C server. A local caching proxy > is one possibility; the use of an XML Catalog is another. Pointers to further information > on these is available in the blog post at [2]. > > - As software developers, you should ensure that your software can use XML Catalogs > for stable resources like the DSig schema, and that it is easy for the user to tell the > software where to find the catalog. (My personal view is that it's helpful if you ship a > catalog with your software and make use of a catalog the default, but some smart > people disagree with me on that.) I have been packaging xhtml1 DTDs for Red hat and related Linux distribution for a decade or so. One thing that the W3C system team could do is proactively provide catalogs updates that could be added for all sorts of DTDs and Schemas that are made public by W3C. Being the issuing authority this is less likely to be incomplete or outdated. They also have the statistics needed to know which ones are the most asked for and hence which one would be the most effective to cache data. I'm sure SVG, or more recent XHTML versions would be useful additions to the existing xhtml1-dtds, for example. Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
Received on Monday, 4 March 2013 15:58:43 UTC