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 3620 - Policy Attachment to WS-Addr EndpointReferences
Summary: Policy Attachment to WS-Addr EndpointReferences
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Attachment (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Glen Daniels
QA Contact: Web Services Policy WG QA List
Keywords: futureConsideration
Depends on:
Reported: 2006-08-23 14:54 UTC by Glen Daniels
Modified: 2008-12-02 22:45 UTC (History)
1 user (show)

See Also:


Description Glen Daniels 2006-08-23 14:54:32 UTC

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.


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
Comment 1 Paul Cotton 2006-09-13 23:28:53 UTC
This was discussed at the Sep F2F meeting:

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.