- From: <Simon.Cox@csiro.au>
- Date: Sun, 5 Sep 2004 19:31:55 +0800
- To: <www-xml-schema-comments@w3.org>
- Cc: <w3c-xml-schema-ig@w3.org>
John Hockaday wrote: "There needs to be some sort of PUBLIC identifier and Oasis Catalogue system within the XML Schema specification so that one can identify on his or her system where the validators can find the local copies of the XML Schemas and so that one doesn't have to edit his or her XML Schemas and XML Document Instances to find the location of the relative XML Schemas." It is not clear that this is an issue related to the XML Schema specification. It is made quite clear in the XML Schema specification that the values of both xsi:schemaLocation and xsd:schemaLocation attributes should be treated as "hints" (http://www.w3.org/TR/xmlschema-1/#xsi_schemaLocation, http://www.w3.org/TR/xmlschema-1/#composition-schemaImport) for precisely the reasons described - it is legal for a processor to prefer a different source for descriptions of the components. So in fact it is a processor configuration issue. And most XML Schema processors *do* provide at least some support for OASIS Catalog - in the case of XML Spy this is quite limited, but it is there so the tool may be configured. However, I believe that the issue is really the "processing model" for which there is or was another W3C working group. See http://www.xml.com/pub/a/2002/03/13/processing-model.html and http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405/ ______ Simon.Cox@csiro.au CSIRO Exploration & Mining 26 Dick Perry Avenue, Kensington WA 6151 PO Box 1130, Bentley WA 6102 AUSTRALIA T: +61(8) 6436 8639 F: +61(8) 6436 8555 C: +61(4) 0330 2672 callto://dr_shorthair http://www.em.csiro.au
Received on Sunday, 5 September 2004 11:32:30 UTC