[Bug 8293] New: fuzzy definition of a "metadata resource"

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8293

           Summary: fuzzy definition of a "metadata resource"
           Product: WS-Resource Access
           Version: PR
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MetadataExchange
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


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


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Saturday, 14 November 2009 02:09:12 UTC