- From: Katy Warr <katy_warr@uk.ibm.com>
- Date: Mon, 2 Nov 2009 16:12:52 +0000
- To: Asir Vedamuthu <asirveda@microsoft.com>
- Cc: public-ws-resource-access@w3.org
- Message-ID: <OFF48813EB.E7A6E58B-ON80257662.0057DB17-80257662.00591117@uk.ibm.com>
Hi Asir
The example only returns one WSDL (which happens to have some others
imported within it) so we can tell (implicitly) that that's the root and
so no semantics are required. Sorry if I have not understood your
question?
Best regards
Katy
From:
Asir Vedamuthu <asirveda@microsoft.com>
To:
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Date:
02/11/2009 01:24
Subject:
RE: [Bug 8031] New: WS-Mex: Distinguishing the 'main' metadata
> the one that would be returned from HTTP GET
> targeted at <endpoint>?WSDL
Are there any semantics associated with a WSDL returned by
http://<endpoint>?WSDL? For instance, what is the semantics associated
with a WSDL that is returned by such a Get request and contains a few
import statements (see below)?
<definitions name="StockQuote"
targetNamespace="http://example.com/stockquote/definitions"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://example.com/stockquote/definitions"
location="http://example.com/stockquote/definitions1.wsdl"/>
<import namespace="http://example.com/stockquote/definitions"
location="http://example.com/stockquote/definitions2.wsdl"/>
</definitions>
Regards,
Asir S Vedamuthu
Microsoft Corporation
-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org [
mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf
Of bugzilla@wiggum.w3.org
Sent: Friday, October 23, 2009 6:36 AM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 8031] New: WS-Mex: Distinguishing the 'main' metadata
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031
Summary: WS-Mex: Distinguishing the 'main' metadata
Product: WS-Resource Access
Version: PR
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: MetadataExchange
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: katy_warr@uk.ibm.com
QAContact: public-ws-resource-access-notifications@w3.org
A GetMetadata request may return multiple documents all of the same
dialect.
How does the client know which of these documents is the 'root' document?
For example (this is a side note mentioned in 7912):
When multiple WSDL documents* are returned from GetMetadata, how do we
distinguish the 'real' one - i.e. the one that would be returned from HTTP
GET
targeted at <endpoint>?WSDL ?
Note that there might be >1 root documents - for instance, in the case of
one
WSDL for soap 1.1 and one for SOAP 1.2.
*Multiple WSDL documents may be returned if operations are implicitly
defined
(via policy) or if WSDL documents are imported.
Proposal:
--------
Here is a starting proposal:
Add an attribute @root to the dialect in order to indicate that the
metadata
section is a 'root' one. Define the meaning of the 'root' document for
each
dialect.
<mex:MetadataSection Dialect='http://schemas.xmlsoap.org/wsdl/
Identifier='http://services.example.org/stockquote'
Root=true>
...
</mex:MetadataSection>
<mex:MetadataSection Dialect='http://schemas.xmlsoap.org/wsdl/
Identifier='http://www.w3.org/2009/09/ws-tra'
Root=false>
...
</mex:MetadataSection>
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Monday, 2 November 2009 16:13:54 UTC