- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 10 Jul 2000 15:03:42 +0100
- To: "Simon St.Laurent" <simonstl@simonstl.com>
- Cc: xmlschema-dev@w3.org
"Simon St.Laurent" <simonstl@simonstl.com> writes: > At 02:49 PM 7/10/00 +0100, Henry S. Thompson wrote: > >True -- if you supply one or more schema docs on the command line, > >that pre-empts other searches. No catalog is necessary. Think of the > >targetNamespace attribute in the supplied schema docs as the left hand > >sides of catalog entries, and the schema docs themselves as the > >right hand sides > > In the long run, though, wouldn't something like FPIs and catalogs make > sense for this kind of work? In the long run[XML Packaging], yes. For XML Schemas, no. Catalogs are a minefield, I don't want to go there. > I don't find targetNamespace useful if I can't find a local copy of the > schema in the first place... Um, I'm lost. We're discussing a case where an instance uses various namespaces, schema documents for which I have local copies of. What it _means_ to have a schema document for a namespace is to have a schema document whose 'targetNamespace' attribute is the name of that namespace. So when I provide those local copies to the schema-validation process, I've essentially provided both LHS (targetNamespace) and RHS (local filename for schema document) for a catalog. ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh W3C Fellow 1999--2001, part-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/
Received on Monday, 10 July 2000 10:03:45 UTC