W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2009

Re: [XML Schema 1.1] What problem is this solving: the ability to define multiple targetNamespaces in a single schema

From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
Date: Mon, 20 Jul 2009 20:58:12 -0600
Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, "xmlschema-dev@w3.org" <xmlschema-dev@w3.org>
Message-Id: <E7A7D90C-9104-4B68-B162-431591EBE68B@blackmesatech.com>
To: "Costello, Roger L." <costello@mitre.org>

On 20 Jul 2009, at 17:42 , Costello, Roger L. wrote:

>
> Hi Folks,
>
> In XSD 1.1 a schema can have multiple targetNamespaces. Presumably  
> this capability was introduced to solve a problem. What problem is  
> it solving?
>

Pedantic note:  I think you must mean that a schema *document*
may in 1.1 have multiple target namespaces.  I've just sent
a note responding to that question.

But after sending it I noticed that you referred to a
schema rather than a schema document.  And at the risk of
being pedantic about a difference which the spec regards
as important and many users appear not to regard as
important at all, I write to point out that as regards
schemas, the presupposition of your question is in error.
XSD schemas have always had the ability to include
components in multiple namespaces -- indeed, almost all
schemas are multi-namespace schemas, since any user-defined
schema will typically include components (elements, types,
...) in the user's target namespace, and will also include
all the built-in datatypes in the XSD namespace.


-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************
Received on Tuesday, 21 July 2009 02:58:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:14:04 GMT