|
[XMLSCHEMA-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: [XML Schema 1.1] What problem is this solving: the ability to define multiple targetNamespaces in a single schema
From: <noah_mendelsohn@us.ibm.com>
Date: Mon, 20 Jul 2009 20:08:04 -0400 To: "Costello, Roger L." <costello@mitre.org> Cc: "xmlschema-dev@w3.org" <xmlschema-dev@w3.org> Message-ID: <OF30C6FA5E.2F8A15A9-ON852575FA.0000336F-852575FA.000053C7@lotus.com> 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@mitre.org> Sent by: xmlschema-dev-request@w3.org 07/20/2009 07:42 PM To: "xmlschema-dev@w3.org" <xmlschema-dev@w3.org> 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? /RogerReceived on Tuesday, 21 July 2009 00:04:40 GMT |
Subscribe in XML format
|

![Re: [XML Schema 1.1] What problem is this solving: the ability to define multiple targetNamespaces in a single schema](/images/get_stylus.gif)




