RE: [Bug 8291] New: editorial: what is an "explicit request for metadata"?

Looks okay. Shall we close issue 8291?

Regards,

Asir S Vedamuthu
Microsoft Corporation

-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org [mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
Sent: Friday, November 13, 2009 3:37 PM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 8291] New: editorial: what is an "explicit request for metadata"?

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

           Summary: editorial: what is an "explicit request for metadata"?
           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 2.2 "Example" contains the following text right before Example 2-3:

"While the WS-Policy of the Web service endpoint could be retrieved using a
WS-Transfer Get request directed to the endpoint identified by the
mex:MetadataReference element in lines 74-78 of Example 2-2, some endpoints MAY
choose to support explicit request for metadata."

One has to presume that an "explicit request for metadata" involves the use of
the GetMetadata operation, but the spec doesn't come right out and say that.

Proposal:

"While the WS-Policy of the Web service endpoint could be retrieved using a
WS-Transfer Get request directed to the endpoint identified by the
mex:MetadataReference element in lines 74-78 of Example 2-2, some endpoints MAY
support explicit requests for metadata via the GetMetadata operation."


-- 
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 Friday, 20 November 2009 18:30:41 UTC