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 4178 - Declaration of policy domains in policy expressions
Summary: Declaration of policy domains in policy expressions
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: LC
Hardware: Macintosh All
: P2 normal
Target Milestone: ---
Assignee: Fabian Ritzmann
QA Contact: Web Services Policy WG QA List
Keywords: futureConsideration
Depends on:
Reported: 2007-01-10 11:04 UTC by Fabian Ritzmann
Modified: 2007-01-17 19:10 UTC (History)
1 user (show)

See Also:


Description Fabian Ritzmann 2007-01-10 11:04:38 UTC

Declaration of policy domains in policy expressions

Description and Justification

An explicit declaration of policy domain is important and improves processing efficiency. Such an explicit declaration could:

   1. Make explicit requirements on intersection and merging.
   2. Allow the policy vocabulary to be explicitly declared thus alleviating the need to iterate through all assertions contained in the policy.
   3. Enable the association of semantics with the absence of an assertion.
   4. Facilitate reuse by allowing specialized policy engines to process policies for a specific domain.
   5. Avoid combinatorial explosion in computing policy intersections whereby there must be a way to determine which policies must be intersected with others.

Otherwise, all combinations must be attempted. Combinatorial explosion may render impossible the effective and efficient computability of intersection of large policies.


WS-Policy Framework V.Next


Of identified options, one solution would be to add a new attribute to the Policy element:

/wsp:Policy/@Domains where @Domains could take a list of URIs to indicate the domains that the policy addresses. The URIs are separated by a space similar to the PolicyURI attribute. The domains would define suitable URIs such as the default namespace.

An example of an RM policy with its domain:

<wsp:Policy wsu:Id="anRMPolicy"

The intersection of policies that address different domains is an empty policy. Policies can be merged by adding up the URIs of the respective Domains attributes and applying the regular policy merge algorithm. Nested policies MAY use the Domains attribute to declare the domains they address. The top-level policy element SHOULD enumerate all Domains that its nested policies are declaring in their respective Domains attribute.
Comment 1 Christopher Ferris 2007-01-17 19:10:24 UTC
RESOLUTION: everybody fine to close 4178 with "won't fixed" and "futureConsideration"