Re: Question re: WSDL 2.o and (schema) xs:import

James,

We aren't changing the behavior of xs:import. If a WSDL document refers to 
an XSD namespace then it MUST declare that namespace by an explicit 
<xs:import>, For example, suppose we have 3 documents, A.wsdl, B.xsd, and 
C.xsd, and suppose their target namespaces are A, B, and C. Suppose 
further that B.xsd imports C, and that A.wsdl refers to types from both B 
and C. Then A.wsdl MUST import both B and C. Even though B.wsd imports C, 
A.wsdl must still explicitly import C. This is what we mean by <xs:import> 
not being transitive. That's precisely how it works in XSD too.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/



"RDBMS" <RDBMS@aol.com> 
Sent by: www-ws-desc-request@w3.org
07/11/2005 07:40 PM
Please respond to
"RDBMS"


To
"Booth, David \(HP Software - Boston\)" <dbooth@hp.com>
cc
<www-ws-desc@w3.org>, Arthur Ryman/Toronto/IBM@IBMCA
Subject
Re: Question re: WSDL 2.o and (schema) xs:import






Thank you for your response re: WSDL 2.0 and xs:import.
 
Actually, what I had read and interpreted from the WSDL 2.0 draft is that 
cascading schema imports (xs:import) are not supported.
 
Perhaps a misinterpretation on my part of the "transitive" editor comment 
in the draft, but as I read the detail, it appeared that a schema 
referenced by xs:import within the WSDL <types/> section that also then 
imports another schema directly from within the first schema - but 
directly from within the schema, not another WSDL xs:import declaration 
(and so on) would not be supported by WSDL 2.0.
 
This capability (schema xs:import to schema, xs:import to schema, 
xs:import to schema etc.) is supported by XML Schemas. I can create a 
schema that imports another schema (or several schemas) of a different 
namespace, and that schema can then import yet another schema (or several 
schemas) of yet another namespace, and so on.
 
This scenario is quite common in my experience and allows for broad scale 
reuse of modular and standard sub-schemas (e.g. representing data 
standards, enterprise data structures, common type libraries, etc.).
 
My question/concern was that as I read the WSDL 2.0 draft with the comment 
re: schema import not being transitive, this common and critical 
capability of XML schemas (import to import to import and so on) would not 
be allowed or supported when the primary/parent schema (the one doing all 
the subordinate imports) is imported within the WSDL <types/> section.
 
Hopefully this makes some sense ;-)
 
Any information, clarification, or confirmation is much appreciated !
Thank you !
J. Bean
P.O. Box 30171
Phoenix, AZ  85046-0171
 
RDBMS@aol.com
XML-Guy@hotmail.com
----- Original Message ----- 
From: Booth, David (HP Software - Boston) 
To: RDBMS 
Cc: www-ws-desc@w3.org ; Arthur Ryman 
Sent: Monday, July 11, 2005 4:12 PM
Subject: RE: Question re: WSDL 2.o and (schema) xs:import

James,
 
Perhaps you were thinking of wsdl:include or xs:include?
-----Original Message-----
From: Arthur Ryman [mailto:ryman@ca.ibm.com] 
Sent: Monday, July 11, 2005 5:20 PM
To: RDBMS
Cc: Booth, David (HP Software - Boston); www-ws-desc@w3.org; 
www-ws-desc-request@w3.org
Subject: Re: Question re: WSDL 2.o and (schema) xs:import


James, 

We don't want to change the behavior of <xs:import>. It is not transitive 
in XSD. You need to explicitly import a namespace in any XSD that refers 
to it. 

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/ 


"RDBMS" <RDBMS@aol.com> 
Sent by: www-ws-desc-request@w3.org 
06/28/2005 08:32 PM 


To
<www-ws-desc@w3.org> 
cc
<dbooth@hp.com> 
Subject
Question re: WSDL 2.o and (schema) xs:import








I've been doing some research on the draft of WSDL 2.0 and found the WSDL 
2.0 editorial note re: "xs:import not being transitive". 
  
I am somewhat concerned as xs:import (both cascading through and across 
multiple target namespaces) is both a valuable and critical capability of 
XML Schema. 
  
The ability to import a cascading chain of namespace qualified resources 
from multiple schemas (and multiple targetNamespaces) is core to reuse of 
modular schema artifacts. 
  
I am not sure why this capability would be eliminated from WSDL ? 
  
I've not found further annotation as to discussion or possible resolution 
of the question and was hoping that you might provide additional insight 
or perspective, or possibly help to influence the WSDL 2.0 to consider how 
important this capability is. 
  
Thank you ! 
James Bean
RDBMS@aol.com