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 10768 - MEX: Optionality of GetWSDL
Summary: MEX: Optionality of GetWSDL
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 14:05 UTC by Doug Davis
Modified: 2011-01-11 22:03 UTC (History)
0 users

See Also:

Attachments

Comment 1 Doug Davis 2010-09-27 14:10:24 UTC 
See:  http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Sep/0001.html

Proposal:
Modify the GetWSDLResponse:

Current text:
[Body]/mex:GetWSDLResponse/xs:any
    When the GetWSDLResponse element contains any child elements, the first element MUST either be the WSDL metadata document, or a reference to the WSDL metadata document, of the endpoint. Any extension elements MUST appear after the WSDL document/reference. The absence of any child elements indicates that the endpoint does not have any WSDL document, or additional metadata, associated with it. 

Add before the "Any extension elements..." sentence:
While an endpoint MAY choose to return a reference to the WSDL, it is 
STRONGLY RECOMMENDED that the WSDL metadata document itself be returned.  
If a requester would like a reference to the WSDL then it can use the 
GetMetadata operation specifying the appropriate Content URI.
Comment 2 Doug Davis 2010-09-27 14:24:23 UTC 
testing
Comment 3 Robert Freund 2010-09-28 19:42:12 UTC 
Resolved as proposed