This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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)?
General Proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0000.html
Another proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0007.html
Further discussion and proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0020.html
And, some additional discussion at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0047.html
Latest proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0012.html
Please find the latest proposal dated Jan 5th at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0015.html
resolved with the proposal at http://www.w3.org/2002/ws/ra/10/03/MOAPv2.zip with an additional example and explanatory test (12.2) described in http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Mar/0000.html and the addition of an editor's note saying that these parts are still under discussion in the WG at example 9.1, text in 11.1 (nexted policy assertions) and example 8.5