This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8031 - WS-Mex: Distinguishing the 'main' metadata
Summary: WS-Mex: Distinguishing the 'main' metadata
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Katy Warr
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-23 13:36 UTC by Katy Warr
Modified: 2010-03-17 11:34 UTC (History)
2 users (show)

See Also:


Attachments

Description Katy Warr 2009-10-23 13:36:19 UTC
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>
Comment 1 Asir V Selvasingh 2009-11-02 01:40:29 UTC
Discussion at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0006.html
Comment 2 Robert Freund 2009-11-05 21:20:23 UTC
Use case is to allow the mex metadata consumer can determine if a wsdl document is intended to be treated as implicit.
I.e, that it is feature wsdl
Agreed 2009-11-05
Comment 3 Robert Freund 2009-11-05 21:21:22 UTC
proposed way forward: as part of definition of wsdl dialect in mex spec, we define an optional boolean attribute, called @isImplicit, which if present with value true indicates that this is feature wsdl implied value is 'false'
to be re-visited 2009-11-06
Comment 4 Robert Freund 2009-12-02 17:38:18 UTC
Connected possibly with 7986 any may be simultaneously resolved
Comment 5 Robert Freund 2010-03-09 21:54:43 UTC
resolved by resolution to 6463 which see