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 5045 - Why did intersection fail?
Summary: Why did intersection fail?
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: PR
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Web Services Policy WG QA List
Keywords: futureConsideration
Depends on: 3616 3639
  Show dependency treegraph
Reported: 2007-09-12 21:43 UTC by Ashok Malhotra
Modified: 2007-09-26 16:53 UTC (History)
0 users

See Also:


Description Ashok Malhotra 2007-09-12 21:43:12 UTC
The current Framework spec says that the result of intersection is zero or more compatible policy alternatives.  If the intersection fails, there are zero compatible alternatives but there is no way to indicate why the intersection failed.  (If more than one alternative intersected we are in the space of issue "Which Policy Alternative was Selected" which was marked vNext and "won't fix".)

We have had customers ask for feedback of the form "these policies are not compatible because Assertion X does not appear in both policies" or "these assertions may be compatible but, unfortunately, have different namespaces".  Thus, some form of feedback on why policies are not compatible would  be very useful.

Perhaps this is part of negotiation:
Comment 1 Christopher Ferris 2007-09-26 16:52:49 UTC
RESOLUTION: close 5045 with no action, mark as and add dependencies to related issues 3616 and 3639