W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2002

RE: import in import and namespace

From: Mark Feblowitz <mfeblowitz@frictionless.com>
Date: Mon, 14 Jan 2002 09:06:03 -0500
Message-ID: <4DBDB4044ABED31183C000508BA0E97F024D56F9@fcpostal.frictionless.com>
To: "'Bruno Chatel'" <bcha@chadocs.net>, "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
Cc: xmlschema-dev@w3.org
Many bugs in processing Schema have been fixed in Xerces 2.0.0B4, especially
several problems with the proper handling of imports and includes.

If you seem to be having trouble getting "the right thing" to happen with
Xerces, make sure you try the most recent version - the problem may be with
the older Xerces version, not with your understanding of the Rec.


Mark Feblowitz                                   [t] 617.715.7231
Frictionless Commerce Incorporated     [f] 617.495.0188 
XML Architect                                     [e]
400 Technology Square, 9th Floor 
Cambridge, MA 02139 

 -----Original Message-----
From: 	Bruno Chatel [mailto:bcha@chadocs.net] 
Sent:	Sunday, January 13, 2002 8:10 AM
To:	Henry S. Thompson
Cc:	xmlschema-dev@w3.org
Subject:	Re: import in import and namespace

> > I have the following schema :
> > 
> > s1.xsd : targetNameSpace ns1
> >     importing s2.xsd with NameSpace ns2    
> >         importing s3.xsd with NameSpace ns1 (the "main"
> > 
> > Is this modularization strategy allowed ? 
> Yes.

It was my opinion too. 

> > 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.

s3.xsd is not read by the TraverseSchema class when processing 
import element. (note : the version of xerces used is xerces_j 1.4.3).
It seems to be a bug. 

> > 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?

Because s2.xsd is used "single" (directly for some documents). 

Thanks !

-- bruno -- 
Bruno Chatel
Tel : (+33)[0] 4 96 11 14 57
Email : bcha@chadocs.com
Received on Monday, 14 January 2002 09:06:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:26 GMT