5045 2007-09-12 21:43:12 +0000 Why did intersection fail? 2007-09-26 16:53:02 +0000 1 1 1 Unclassified WS-Policy Framework PR PC Windows XP RESOLVED WONTFIX futureConsideration P2 normal --- 3616 3639 1 ashok.malhotra fsasaki public-ws-policy-qa oldest_to_newest 16520 0 ashok.malhotra 2007-09-12 21:43:12 +0000 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" http://www.w3.org/Bugs/Public/show_bug.cgi?id=3639 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: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3616 16816 1 chrisfer 2007-09-26 16:52:49 +0000 RESOLUTION: close 5045 with no action, mark as v.next and add dependencies to related issues 3616 and 3639 See http://www.w3.org/2007/09/26-ws-policy-irc#T16-52-34