This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6463 - MEX: Attaching Policy to WS-Mex GetMetadata
Summary: MEX: Attaching Policy to WS-Mex GetMetadata
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Katy Warr
QA Contact: notifications mailing list for WS Resource Access
Keywords: needsAction
Depends on: 6721
Blocks: 7728
  Show dependency treegraph
Reported: 2009-01-21 14:44 UTC by Katy Warr
Modified: 2010-03-17 11:09 UTC (History)
3 users (show)

See Also:


Description Katy Warr 2009-01-21 14:44:34 UTC
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:

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)?
Comment 1 Robert Freund 2009-02-16 02:45:09 UTC
General Proposal at
Comment 2 Asir V Selvasingh 2009-11-02 01:38:43 UTC
Another proposal at
Comment 3 Katy Warr 2009-12-01 19:08:30 UTC
Further discussion and proposal:
Comment 4 Asir V Selvasingh 2009-12-01 19:27:01 UTC
And, some additional discussion at 
Comment 6 Asir V Selvasingh 2010-01-19 19:42:18 UTC
Please find the latest proposal dated Jan 5th at
Comment 7 Robert Freund 2010-03-09 21:54:05 UTC
resolved with the proposal at
with an additional example and explanatory test (12.2) described in
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