- From: Martin Gudgin <mgudgin@microsoft.com>
- Date: Tue, 19 Jul 2005 08:24:34 -0700
- To: "Amelia A Lewis" <alewis@tibco.com>
- Cc: <ryman@ca.ibm.com>, <www-ws-desc@w3.org>
> -----Original Message----- > From: Amelia A Lewis [mailto:alewis@tibco.com] > Sent: 19 July 2005 16:05 > To: Martin Gudgin > Cc: ryman@ca.ibm.com; www-ws-desc@w3.org > Subject: Re: Fw: Question re: WSDL 2.0 and (schema) xs:import > > On Tue, 19 Jul 2005 08:05:07 -0700 > "Martin Gudgin" <mgudgin@microsoft.com> wrote: > > 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. > > Since the "example" schemas provided don't actually contain any > declarations, it's impossible to tell. Right. Arthur could you directly ask James whether any of his schemas contain references to components in namespaces that are not explicitly imported ( and are *not* the targetNamespace)? > > Certainly, though, if the hypothetical SchemaA contained an element > declaration which referenced a complex type defined in SchemaC or > SchemaD, a conformant XML Schema processor would toss its cookies, > lacking an import in SchemaA for either of those schemas. That's the > behavior we want for WSDL, as well. Absolutely. Gudge > > Amy! > -- > Amelia A. Lewis > Senior Architect > TIBCO/Extensibility, Inc. > alewis@tibco.com >
Received on Tuesday, 19 July 2005 15:25:59 UTC