Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: noah_mendelsohn@--.---.---
To: "Costello, Roger L." <costello@-----.--->
Date: 7/21/2009 12:05:00 AM
If I remember correctly, there was a concern expressed by some users about 
an inability in XSD 1.0 to succeed in restricting certain complex types 
when the content models involved more than one namespace.  I don't think I 
can reproduce an example offhand, but I'm fairly sure that was the 
original motiviation.

Noah

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








"Costello, Roger L." <costello@m...>
Sent by: xmlschema-dev-request@w...
07/20/2009 07:42 PM
 
        To:     "xmlschema-dev@w..." <xmlschema-dev@w...>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        [XML Schema 1.1] What problem is this solving: the 
ability to  define multiple targetNamespaces in a single schema



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?

/Roger





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