- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 22 Apr 2002 08:57:49 +0100
- To: noah_mendelsohn@us.ibm.com
- Cc: "Dare Obasanjo" <dareo@microsoft.com>, "Stanley Guan" <stanley.guan@oracle.com>, xmlschema-dev@w3.org
noah_mendelsohn@us.ibm.com writes: > I've only followed some of this thread. That said: isn't it reasonable > that I might want to define xml:lang, for purposes of my schema, as being > an enumeration of say {en,fr}? Why prevent that? Agreed. > I think it would be a good thing if many parsers took switches to force > loading of particular schemas, to force schemaLocation to be honored on > import, etc. Of course, there can be no conflict among (global) > definitions of a given element or attribute. Agreed. In general XSV supports this, in that schema documents offered on the command line are always loaded and take precedence over e.g. schemaLocation in <import>. However since it uses the 'official' xml schema in validating schema documents, it refuses to allow that one to be overriden -- a bug, I guess, but not high on my list to fix. ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh W3C Fellow 1999--2002, 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/ [mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Monday, 22 April 2002 03:58:04 UTC