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 3719 - Levels of indirection for policy references
Summary: Levels of indirection for policy references
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Attachment (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Web Services Policy WG QA List
: 3722 (view as bug list)
Depends on:
Reported: 2006-09-13 16:45 UTC by Paul Denning
Modified: 2006-10-04 18:34 UTC (History)
0 users

See Also:


Description Paul Denning 2006-09-13 16:45:14 UTC

WS-PolicyAttachment should support more levels of indirection in terms of policy references.

My email at [1] touched on this.

It should be possible to have a policy reference in a WSDL file point to a UDDI tModel that then points to a WS-Policy document.

Also, for a UDDI tModel that points to a WSDL that includes a policy attachment, have a categoryBag that marks the tModel as a policy reference.
B.2 should be "checked" since currently it only allows one valid value, "policy".  You should consider additional values, such as "policyReference", to be used when the tModel does not point directly to the policy, but instead points to the WSDL with a policy reference.  Perhaps the tModel points to a RDDL document, which points to WSDL, which points to WS-Policy.

WS-Policy and UDDI registries will be important for SOA governance, and we need to allow more levels of indirection, yet be able to locate related things in UDDI.
Comment 1 Paul Cotton 2006-09-14 21:29:23 UTC
*** Bug 3722 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Roth 2006-09-29 21:22:16 UTC
You can solve this problem by having your policy references point to a URI that references the "current" policy.  Section 4.3.4 of the Policy Framework states: "The IRI included in the retrieved policy expression, if any, MAY be different than the IRI used to retrieve the policy expression."  

For example, you could have policy reference like this:

<wsp:PolicyReference URI="urn:currentPolicy" />

That points to a policy like this:

<wsp:Policy Name="urn:myUpdatedPolicy" >

How you resolve external policy references is implementation specific, which allows you to version the policy independently of the URI used to reference the policy.  
Comment 3 Paul Cotton 2006-10-04 17:35:37 UTC
Resolved at the Oct 4 meeting. See:

See description in:

Comment 4 Paul Cotton 2006-10-04 18:34:32 UTC
The currect URI for the previous comment is obviously: