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 3722 - Levels of indirection for policy references
Summary: Levels of indirection for policy references
Status: RESOLVED DUPLICATE of bug 3719
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-13 17:41 UTC by Paul Denning
Modified: 2006-09-14 21:29 UTC (History)
0 users

See Also:

Attachments

Description Paul Denning 2006-09-13 17:41:09 UTC 
[1] http://lists.w3.org/Archives/Public/public-ws-policy/2006Aug/0139

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 Asir V Selvasingh 2006-09-14 00:54:40 UTC 
This is a duplicate of 3719 (see http://www.w3.org/Bugs/Public/show_bug.cgi?id=3719
Comment 2 Paul Cotton 2006-09-14 21:29:23 UTC 
Deemed as a duplicate of 3719 at the Sep F2F:
http://www.w3.org/2006/09/14-ws-policy-irc#T21-28-44 

*** This bug has been marked as a duplicate of bug 3719 ***