W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2007

RE: multiple namespaces

From: Michael Kay <mike@saxonica.com>
Date: Mon, 23 Apr 2007 16:40:30 +0100
To: "'Andrew Welch'" <andrew.j.welch@gmail.com>, <noah_mendelsohn@us.ibm.com>
Cc: <xmlschema-dev@w3.org>
Message-ID: <00fb01c785bd$b9d33bd0$6401a8c0@turtle>

> The keys points here are:
> 
> - there are two namespaces
> - each namespace contains elements in the other namespace
> 
> In order to model this I created two schema documents ns1.xsd 
> and ns2.xsd which import each other:

Correct.
> 
> I'd like any comments on this approach - its seems strange to 
> have circular imports

Think Java "import" rather than XSLT "import". It's not at all strange in
Java for two modules to import each other. In XSD, import means "this module
references components defined in that module".

, and when referencing the simpleType 
> and the group prefixes are needed - unless as Mike says I add 
> a default namespace, which I think would make the top of the 
> schema document:
> 
> targetNamespace="firstNamespace"
> xmlns:ns1="firstNamespace"
> xmlns="firstNamespace"
> 
> ...which is fine but a little non-intuitive at the moment - 
> is there a preferred approach?

One sees different coding styles, but it's certainly not unusual to see
schema documents that are just like this: the targetNamespace is bound both
to an explicit prefix and to the default namespace. Personally I tend to use
the prefix, it helps to remind the reader what's going on and makes it
easier to cut-and-paste across schema documents.

Michael Kay
http://www.saxonica.com/
Received on Monday, 23 April 2007 15:40:56 GMT

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