W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > November 2009

Re: [Bug 6463] New: Attaching Policy to WS-Mex GetMetadata

From: Gilbert Pilz <gilbert.pilz@oracle.com>
Date: Mon, 02 Nov 2009 11:32:23 -0800
Message-ID: <4AEF33C7.4080909@oracle.com>
To: Asir Vedamuthu <asirveda@microsoft.com>
CC: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
First off, it's not clear that a WSDL will always exist. For example, 
what WSDL would you use for a wsrm:AcksTo EPR?

Secondly, as a practical matter, adding an entire WSDL+Policy to an EPR 
will increase the size of that EPR 10 times or more.

Finally, attaching a WSDL doesn't save the EPR consumer any effort 
w/regards to computing the effective policy of the endpoint. As Antoine 
said in his original email [1]:

    Ideally, there should be an easy way to directly attach an endpoint
    effective policy to the EPR, in order to bypass the usual complex
    algorithm that the client must implement to compute the endpoint
    effective policy, which is not practical for some embedded clients

[1] 
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Oct/0027.html

- gp

On 11/1/2009 5:37 PM, Asir Vedamuthu wrote:
> There is a simple, natural solution - embed a WSDL (using MEX in an EPR) that specifies binding/port information for the MetadataExchange portType at http://www.w3.org/2009/09/ws-mex/metadataexchange.wsdl and attach policy expressions to bindings, as appropriate. This is specifically covered by some prose in the current version of WS-MetadataExchange draft [1]:
>
> "In particular, the mechanisms described in 7 Metadata in Endpoint References allow issuers of endpoint references to include sufficient protocol binding information to allow requesters to issue a Get request against a metadata resource, or a Get Metadata request against a service endpoint, in order to retrieve all the information needed to use the service."
>
> Proposal: close issue 6463 without any action!
>
> [1] http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090924/#Bootstrapping-Metadata-Retrieval 
>
> 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: Wednesday, January 21, 2009 6:45 AM
> To: public-ws-resource-access-notifications@w3.org
> Subject: [Bug 6463] New: Attaching Policy to WS-Mex GetMetadata
>
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463
>
>            Summary: Attaching Policy to WS-Mex GetMetadata
>            Product: WS-Resource Access
>            Version: PR
>           Platform: PC
>         OS/Version: Windows XP
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: MetadataExchange
>         AssignedTo: public-ws-resource-access-notifications@w3.org
>         ReportedBy: katy_warr@uk.ibm.com
>
>
> We should consider clarifying or recommending how policy should be associated
> with a WS-MetadataExchange GetMetadata request.  ('Policy' might be existing
> policies such as WS-SecurityPolicy or potential new assertions, as described in
> issue 6406 here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406).
>
> A GetMetadata operation's policy cannot be attached within the Web service
> endpoint's WSDL because:
> In order for a client to establish the WS-Mex GetMetadata policy, it would need
> to issue a GetMetadata(WSDL) request at the web service endpoint...but in order
> to issue a GetMetadata request at the endpoint it would need to establish the
> WS-Mex GetMetadata policy...
>
> The issue here is: what is the correct way to bootstrap the bootstrap (without
> entering an infinite loop)?
>
>
> --
> Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
>
>
>
>   


Received on Monday, 2 November 2009 19:34:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:15 GMT