- From: David Booth <dbooth@w3.org>
- Date: Thu, 07 Oct 2004 12:25:35 -0400
- To: Pete Hendry <peter.hendry@capeclear.com>
- Cc: Glen Daniels <gdaniels@sonicsoftware.com>, Jeehong Min <jeehongm@parasoft.com>, WS Description List <www-ws-desc@w3.org>
FYI, Michael Sperberg-McQueen also wrote to the XML Schema IG about this issue on their members-only list: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Oct/0001.html On Tue, 2004-10-05 at 21:50, Pete Hendry wrote: > Rather than say you cannot be clear about it why not make a clear statement: > > It is not permitted and if it is present then it is an error. > > Nothing ambiguous there and it clears up the issue. It is a lot easier > for an implementation to detect this and error than it is to try to work > around it merging schemas and such. Is there a purpose in allowing it? > > Pete > > David Booth wrote: > > >This is an interesting question, and I think it needs to be clarified in > >our spec, in case others also run into this issue. I've just written to > >the XML Schema group for clarification from an XML Schema point of view: > >http://lists.w3.org/Archives/Public/www-xml-schema-comments/2004OctDec/0001.html > > > >Perhaps we should suggest that WSDL authors avoid doing this, in order > >to avoid the issue, if we cannot be clear about whether or not it is > >permitted and what it means. > > > > > >On Mon, 2004-10-04 at 11:24, Glen Daniels wrote: > > > > > >>Jeehong: > >> > >>As long as there is no overlap between the component definitions in > >>multiple schema containers for the same namespace, I think this should > >>work just fine. If there is overlap, we simply need to follow what the > >>schema spec says about how to resolve repeated components in a schema > >>(I'm not sure, though, if that's fault, first-one-wins, or > >>last-one-wins...). > >> > >>--Glen > >> > >> > >> > >>>-----Original Message----- > >>>From: www-ws-desc-request@w3.org > >>>[mailto:www-ws-desc-request@w3.org] On Behalf Of Jeehong Min > >>>Sent: Monday, September 27, 2004 12:48 PM > >>>To: www-ws-desc@w3.org > >>>Subject: Can multiple inline schemas have same targetNamespace? > >>> > >>>I would appreciate it if you could address the following > >>>issue that I have seen in WSDLs of 2 customers in the past month. > >>> > >>>One vendor's SOAP stack is creating WSDLs with multiple > >>>inline schemas that have the same namespace. > >>> > >>>Here's an example: > >>><wsdl:definition> > >>><wsdl:types> > >>><xs:schema targetNamespace="a"> > >>>types and elements > >>></xs:schema> > >>><xs:schema targetNamespace="a"> > >>>different types and elements > >>></xs:schema> > >>><xs:schema targetNamespace="b"> > >>>whatever > >>></xs:schema> > >>></wsdl:types> > >>>... > >>><wsdl:definition> > >>> > >>>It's not clear to me whether the above is legal or not (two > >>>schemas with the same targetNamespace="a"). Should XML > >>>parsers for WSDL be smart enough to handle the above? Or > >>>should parsers report errors? > >>> > >>>-- > >>>Jeehong Min > >>>Software Engineer > >>>SOAPtest Development > >>>Parasoft Corporation > >>> > >>>"We Make Software Work" > >>> > >>> > >>> -- David Booth W3C Fellow / Hewlett-Packard
Received on Thursday, 7 October 2004 16:25:38 UTC