RE: wsdl:import and xsd:import use clarification in WSDL spec

The status quo in WSDL 1.2 is as follows ( the spec is not entirely
up-to-date in this regard ):

1.	You can use wsdl:import to bring in a WSDL with a different
targetNamespace to you. The WSDL components in that WSDL are visible to
you. The XSD components ( if any ) in that WSDL are NOT visible to you.

2.	You can use wsdl:incoude to bring in a WSDL with the same
targetNamespace as you. The WSDL components in that WSDL are visible to
you. The XSD components ( if any ) in that WSDL are NOT visible to you.

3.	You can use xsd:import as a child of wsdl:types to bring in an
XSD. The XSD components in that XSD are visible to you.

4.	If you have an inline xsd:schema as a child of types, the
components it defines are visible to you, but any components it imports
or includes are NOT.


You will note that 3 and 4 are divergent from the status quo at WS-I

Gudge

> -----Original Message-----
> From: Prasad Yendluri [mailto:pyendluri@webMethods.com] 
> Sent: 04 December 2002 15:51
> To: www-ws-desc@w3.org
> Subject: wsdl:import and xsd:import use clarification in WSDL spec
> 
> 
> 
> Folks,
> 
> Going through the issues list, I am not quite sure of this particular 
> aspect has been captured. Since WS-I BP ruled clearly on 
> this, thought I 
> would bring up and make sure we also accounted for this.
> 
> WS-I BP ruled that the "wsdl:import" statement can only be used to 
> import another WSDL description and the schema "import" 
> statement must 
> be used within a <schema> element in <wsdl:types> to import 
> XML Schema 
> definitions into WSDL. Additionally the BP also ruled that the schema 
> "import" statement must not be used to import schema definitions 
> embedded in line within another WSDL. WSDL with schema 
> definitions can 
> be wsdl:imported as a whole.
> 
> Issue #21 is close but does not seem to address this 
> particular aspect.
> 
> Regards, Prasad
> 
>

Received on Wednesday, 4 December 2002 19:50:38 UTC