- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 25 Sep 2002 08:53:56 +0100
- To: Mark Feblowitz <mfeblowitz@frictionless.com>
- Cc: "'noah_mendelsohn@us.ibm.com'" <noah_mendelsohn@us.ibm.com>, jeni@jenitennison.com, mrowell@openapplications.org, Ryan.Barr@ejgallo.com, xmlschema-dev@w3.org
Mark Feblowitz <mfeblowitz@frictionless.com> writes: > I assume that there's a reason (rooted in theory) for import not to be > treated as an include from another namespace. If so, I'd like to understand > it. If not, I'd like to recommend that future XML Schema recommendations > move in that direction. > > BTW - I've looked around at OAGIS' overlay examples and so far have found > none that contain more than one import from a given namespace. The way the > OAGIS files are structured tends to mimic the adaptor approach, at least for > most cases. > > I did find situations where there is an import from a particular namespace > (e.g., NS1) and an include of a file that imports *different definitions* > from NS1. These seem to fuction properly using MSXML, Xerces-J, and XSV. > Question is, can we rely on this functionality, or must we build adaptors to > reliably handle these cases? Once you import a namespace, you get all the definitions and declarations in the schema the processor builds for that namespace. I'm not clear what you mean by "import different definitions". 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 Wednesday, 25 September 2002 03:54:15 UTC