- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 12 Jan 2002 11:41:38 +0000
- To: "Bruno Chatel" <bcha@chadocs.net>
- Cc: <xmlschema-dev@w3.org>
"Bruno Chatel" <bcha@chadocs.net> writes:
> Hello,
>
> I have the following schema :
>
> s1.xsd : targetNameSpace ns1
> importing s2.xsd with NameSpace ns2
> importing s3.xsd with NameSpace ns1 (the "main" targetNameSpace).
>
> Is this modularization strategy allowed ?
Yes.
> It seems that Xerces does not support this kind of schema.
In what sense, not support? If it gives an error for the nested
import, that's a bug. If it declines to take the s3.xsd hint, that's
not a bug. XSV wouldn't either.
> Indeed, in the GrammarResolverImpl class, a schema is referenced by
> its NameSpace (and not its location), then s3.xsd is not imported
> because xerces considered that ns1 is previously processed (by
> s1.xsd).
That's allowed by the REC: schemaLocation on import is a hint.
Why not include s3.xsd from s1.xsd?
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 Saturday, 12 January 2002 06:41:41 UTC