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

RE: Importing schemata into WSDL

From: Don Mullen <donmullen@tibco.com>
Date: Tue, 15 Oct 2002 09:08:44 -0400
Message-ID: <339902DC0E58D411986A00B0D03D843201B24640@extmail.rtp.tibco.com>
To: "'Martin Gudgin'" <mgudgin@microsoft.com>
Cc: Jacek Kopecky <jacek@systinet.com>, WS Description WG <www-ws-desc@w3.org>

Yes, I think this works well, and is what I had in mind as option #3 [1].
Upon reflection, I don't think we need anything indicating what kind of
schema is being imported.  That information would be available in the XML
file (if location used) or already effectively processed and available by
the schema cache.

It seems slightly strange to use the XML Schema namespace <import> to pull
in a Relax NG schema or some other schema language, but it works, and most
processors are going to support XML Schema (perhaps exclusively).


[1] http://lists.w3.org/Archives/Public/www-ws-desc/2002Oct/0051.html

-----Original Message-----
From: Martin Gudgin [mailto:mgudgin@microsoft.com]
Sent: Monday, October 14, 2002 11:57 PM
To: Don Mullen
Cc: Jacek Kopecky; WS Description WG
Subject: RE: Importing schemata into WSDL

I've been thinking a bit more about this. How about

  <xs:import namespace='http://example.org/foo' />
  <xs:import namespace='http://example.org/bar' />

  <xs:schema targetNamespace='http://example.org/baz' >
    <xs:import namespace='http://example.org/quux' />

and say that schema components in foo, bar and baz are visible to WSDL
components but schema components in quux are only visible to the inline
schema. Schema components in foo and bar are NOT visible to the inline

Received on Tuesday, 15 October 2002 09:10:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:40 UTC