This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/mid/80A43FC052CE3949A327527DCD5D6B2701D8CDF9@MAIL01.bedford.progress.com We do not currently have a specification for what it means to attach WS-Policy to an EPR as defined by WS-Addressing [1]. We need one. WS-Addressing is becoming more and more integrated with the WS-* stack, and putting metadata such as WS-Policy into an EPR is a common use case. It's critical that we have a clear and accurate description of how this should work, what is expected of the entities constructing and consuming EPRs containing policy, and where the points of flexibility lie. Proposal: Insert new section 5 before current one in PolicyAttachment spec - "Attaching Policies To EndpointReferences". This section should explain that policies in EPRs function much like policy associated with the Endpoint Policy Subject defined in 4.1.2. We should take care to discuss precedence concerns between WSDL and EPRs passed at runtime, and between new versions of EPRs exchanged as part of an ongoing conversation.
This was discussed at the Sep F2F meeting: http://www.w3.org/2006/09/13-ws-policy-irc#T23-17-46 A strawpoll indicated that 2 members thought this item was in scope for this version of WS-Policy, 3 members felt it was out of scope and 8 did not have an opinion. Due to the WG's tight schedule and the lack of concensus for doing this work the Chair ruled this request was out of scope for WS-Policy 1.5. Two companies stated they could not live with this decision. The Chair maintained his ruling in the face of this opposition. I am marking this issue as for "futureConsideration" so that it can be considered in a future version of WS-Policy. /paulc