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 8296 - MEX: services can't know what metadata a consumer might need
Summary: MEX: services can't know what metadata a consumer might need
Status: CLOSED WONTFIX
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
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-11-14 02:51 UTC by Gilbert Pilz
Modified: 2010-01-27 14:14 UTC (History)
0 users

See Also:


Attachments

Description Gilbert Pilz 2009-11-14 02:51:46 UTC
The description of [Body]/mex:GetMetadata/mex:Dialect has the following sentence:

"When this element is not present, the endpoint SHOULD return all the types of metadata that it deems necessary to communicate with it."

The phrase deems necessary is problematic. Except for simple services, there are generally a number of ways to interact with any service. Metadata of different types and scopes may or may not be necessary depending upon how the consumer intends to interact with the service.  How can the endpoint (more accurately service instance) be expected to know how the consumer intends to interact with it and which metadata is or isn't "necessary"? For example, if WS-RM is optionally supported, is it "necessary" to return the WS-RM feature WSDL?

Proposal: "When this element is not present, the endpoint MUST return all available types of metadata".