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

RE: problem with import/include and XSV type qualified by non-local namespace

From: Colin Mackenzie <colin@elecmc.com>
Date: Thu, 14 Mar 2002 20:41:31 -0000
To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
Cc: <xmlschema-dev@w3.org>
Message-ID: <PJEOKNCGPHICMMDPMNAJMEADCDAA.colin@elecmc.com>

Thanks,

Interestingly MSXML4, TurboXML and XMLSpy do not complain although Xerces-C
agrees with XSV.
MSXML4 and TurboXML seem to have a lot in common as TurboXML thinks that
xs:redefine should have no content whereas MSXML4 only allows one redefine
in a schema (MS have acknowledged this error on the msxml-webrelease
newsgroup)

I did not realise there was a difference in behaviour for import and include
(i.e. in the "included" schema I can reference a type of another schema
where that schema was included in my parent schema).

While all the processors that I have been working with (XML Spy, MSXML4,
Xerces-C, XSV, Turbo XML) can handle multiple identical imports, I have been
trying to work around the namespace coercion bug (see
http://lists.w3.org/Archives/Public/xmlschema-dev/2002Mar/0021.html)
exhibiting itself in MSXML4.

Colin


-----Original Message-----
From: Henry S. Thompson [mailto:ht@cogsci.ed.ac.uk]
Sent: 14 March 2002 17:19
To: Colin Mackenzie
Cc: xmlschema-dev@w3.org
Subject: Re: problem with import/include and XSV type qualified by
non-local namespace


"Colin Mackenzie" <colin@elecmc.com> writes:

> Hi,
>
> I have a top level schema (see top.xsd below) that includes other schemas
> with the same namespace.
>
> These "sub-schemas" use types defined in a schema of another namespace. To
> avoid importing the other schemas multiple times (i.e. once in each sub
> schema) I import the other namespace schema in the top level schema
> (top.xsd).
>
> This seems to work OK in XMLSpy and Turbo XML but using XSV I get an error
> when one of my subschemas attempts to use a type from the other namespace.
> The error is:"attribute type check failed for {None}:type: yours:YourType
is
> qualified by an unimported non-local namespace"
>
> This seems to point to XSV saying that the other namespace schema should
be
> imported in the schema file in which uses that type (rather in the level
> above).
>
> Is XSV correct, have I made a mistake or is this a bug?

A schema document must contain <xs:import>s for every non-local
namespace.  The fact that that document is being included in some
other schema document which has the import does not let it off the
hook.

Are there actually still processors out there that complain about
multiple identical <import>s?

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 Thursday, 14 March 2002 16:10:04 GMT

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