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 8293 - MEX: fuzzy definition of a "metadata resource"
Summary: MEX: fuzzy definition of a "metadata resource"
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: hasProposal
Depends on:
Reported: 2009-11-14 02:09 UTC by Gilbert Pilz
Modified: 2010-03-17 11:26 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2009-11-14 02:09:03 UTC
Section 4 "Metadata Resources" defines a 'metadata resource' as a 'resource' for which metadata has been defined. It defines a 'resource' as 'a Web service that is addressable by an endpoint reference'.

The last sentence in Section 4 states:

"A metadata resource MAY support other operations defined by [WS-Transfer], such as Put (e.g. to allow update of non-static metadata by authorized agents), or other resource management and access specifications (e.g. HTTP, WS-ResourceFramework)."

I don't about WS-ResourceFramework, but I'm pretty certain that HTTP does *not* use EPRs. Therefore, while a piece of software may listen for HTTP GET requests and return some form of metadata, it is not acting as a 'metadata resource' (by the definition of this spec) when it does so as it out of scope of WS-MEX.

In addition, mentioning the use of WS-T Put on a metadata resource leads to a rathole that we've decided that we don't want go down (i.e. "given a service endpoint, how do I create metadata resources associated with that endpoint?" etc.)

Proposal: remove the last sentence in Section 4
Comment 1 Robert Freund 2010-01-12 20:46:04 UTC
resolved as proposed