8293 2009-11-14 02:09:03 +0000 MEX: fuzzy definition of a "metadata resource" 2010-03-17 11:26:39 +0000 1 1 1 Unclassified WS-Resource Access MetadataExchange FPWD All All CLOSED REMIND hasProposal P2 normal --- 1 gilbert.pilz gilbert.pilz dug public-ws-resource-access-notifications oldest_to_newest 29566 0 gilbert.pilz 2009-11-14 02:09:03 +0000 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 30992 1 bob 2010-01-12 20:46:04 +0000 resolved as proposed