W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2005

RE: Fw: Question re: WSDL 2.0 and (schema) xs:import

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Tue, 19 Jul 2005 08:05:07 -0700
Message-ID: <DD35CC66F54D8248B6E04232892B63380660DCC4@RED-MSG-43.redmond.corp.microsoft.com>
To: "Amelia A Lewis" <alewis@tibco.com>, "Arthur Ryman" <ryman@ca.ibm.com>
Cc: <www-ws-desc@w3.org>

It's not clear to me that James is mistaken. But as he doesn't
specifically state whether he is able to *reference* a component from a
namespace he has not imported I can't really tell whether he's mistaken
or not.

James is (I think) looking at this from the perspective of an
*instance*. He has an instance containing elements from namespaces A, B
and C. He can pass schema A (which imports schema B, which imports
schema C ) to his schema validator and it all 'just works'.

He seems to be expecting the same behaviour for WSDL. But in WSDL we're
*referencing* schema components, and we've put the same requirements on
such references (correctly IMO) as those required by XSD.


> -----Original Message-----
> From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org] On Behalf Of Amelia A Lewis
> Sent: 19 July 2005 15:47
> To: Arthur Ryman
> Cc: www-ws-desc@w3.org
> Subject: Re: Fw: Question re: WSDL 2.0 and (schema) xs:import
> On Tue, 19 Jul 2005 10:36:59 -0400
> Arthur Ryman <ryman@ca.ibm.com> wrote:
> > Further discussion from James.
> James appears to badly mistaken about the capabilities of W3C XML
> Schema.  Or, possibly, uses a particular tool that has broken import
> semantics in the manner described (interop is a well-known issue with
> Schema).
> Perhaps we could clarify which tool works in the way described, and
> forward an error report to them?
> Amy!
> -- 
> Amelia A. Lewis
> Senior Architect
> TIBCO/Extensibility, Inc.
> alewis@tibco.com
Received on Tuesday, 19 July 2005 15:06:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:55 UTC