Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [XML Schema 1.1] What problem is this solving: the ability to

From: "C. M. Sperberg-McQueen" <cmsmcq@-------------.--->
To: "Costello, Roger L." <costello@-----.--->
Date: 7/21/2009 2:59:00 AM
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
****************************************************************







transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent