W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2002

RE: Importing schemata into WSDL

From: Don Mullen <donmullen@tibco.com>
Date: Fri, 11 Oct 2002 20:39:19 -0400
Message-ID: <339902DC0E58D411986A00B0D03D843201B24613@extmail.rtp.tibco.com>
To: "'Christopher B Ferris'" <chrisfer@us.ibm.com>
Cc: Amy Lewis <alewis@tibco.com>, "'Jacek Kopecky'" <jacek@systinet.com>, WS Description WG <www-ws-desc@w3.org>, www-ws-desc-request@w3.org
Unfortunately this doesn't work either in all cases.
 
The <xs:schema> would have to have the same targetNamespace as the
<include>d schema.  And if the included file contained the *entire* set of
components for the namespace, this would work.  However, the <include>d file
could <include> other schema documents which would *not* get pulled in.
 
I can give a more specific example if needed.
 
This also has the same limitations as an <import> with forced/required
location.  In an XML environment that includes schema provisioning/caching,
it is sometimes best to only use the namespace, instead of location.
 
Don

-----Original Message-----
From: Christopher B Ferris [mailto:chrisfer@us.ibm.com]
Sent: Friday, October 11, 2002 7:28 PM
To: Don Mullen
Cc: Amy Lewis; 'Jacek Kopecky'; WS Description WG;
www-ws-desc-request@w3.org
Subject: RE: Importing schemata into WSDL



Jacek's points are well taken. Why not then leverage xs:include as that
would 
seem to be more approriate given Jacek's points. 

e.g. 
<wsdl:types> 
        <xs:schema ...> 
                <xs:include
schemaLocation="http://example.org/yadda/mystuff.xsd"/> 
        </xs:schema> 
</wsdl:types> 

Cheers, 

Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624 
Received on Friday, 11 October 2002 20:41:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:21 GMT