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 6679 - MEX's stance towards metadata scope and semantics needs clarification
Summary: MEX's stance towards metadata scope and semantics needs clarification
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
Keywords: needsReview
Depends on:
Reported: 2009-03-11 04:34 UTC by Gilbert Pilz
Modified: 2009-09-16 08:05 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2009-03-11 04:34:09 UTC
The mex:Metadata element acts as a simple container for metadata. WS-MEX makes no assertions about the scope, applicability or semantics of the metadata it transfers. Any correlation between the returned metadata and the resource(s) and/or service(s) exposed by the endpoint must be performed by the requester using information out of band to the WS-MEX exchange.

The above needs to be clarified in normative text within WS-MEX.
Comment 1 Robert Freund 2009-08-06 17:46:51 UTC
When the metadata for an endpoint is not available or is unknown and there is no information on how to retrieve it (e.g. an endpoint reference to a [WS-Transfer] resource representing the metadata), a requester MAY send a Get Metadata request message to that endpoint to retrieve its metadata. 
A requester MAY send a GetMetadata request message to an endpoint to retrieve the metadata associated with that endpoint.
Comment 2 Robert Freund 2009-08-06 17:47:28 UTC
resolved with comment #1