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

RE: importing docs in the same namespace

From: Don Mullen <donmullen@tibco.com>
Date: Tue, 8 Oct 2002 12:54:11 -0400
Message-ID: <339902DC0E58D411986A00B0D03D843201B245B1@extmail.rtp.tibco.com>
To: "'Martin Gudgin'" <mgudgin@microsoft.com>, Sanjiva Weerawarana <sanjiva@watson.ibm.com>, "WS-Desc WG (Public)" <www-ws-desc@w3.org>


+1 -- mirror XML Schema include / import in WSDL

Don

-----Original Message-----
From: Martin Gudgin [mailto:mgudgin@microsoft.com]
Sent: Monday, October 07, 2002 12:26 PM
To: Sanjiva Weerawarana; WS-Desc WG (Public)
Subject: RE: importing docs in the same namespace

[snip]

xsd:include ( like xsd:import ) works at the component level, not the
infoset level. The main differences between the two are as follows:

xsd:import, component based, other namespace, location optional
xsd:include, component based, same namespace, location mandatory
XInclude ( for completeness ), infoset based, same namespace, location
mandatory

The reasoning behind making location optional for xsd:import was that a
given processor may already know about certain namespaces. The reason
behind making location mandatory for xsd:include was that given a
processor is already processing a document with a given targetNamespace
it presumably needs some hint as to how to find the other pieces that
describe said namespace.

I think the cleanest solution is to spec wsdl:import and wsdl:include
the same way the xsd versions work. That way things work the same way in
the wsdl: section of the document as they do in any xsd: sections of the
document.

Gudge
Received on Tuesday, 8 October 2002 12:56:43 GMT

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