W3C home > Mailing lists > Public > public-ws-policy@w3.org > September 2007

[Issue 5045] Re: vNext Issue: Why did intersection fail?

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 13 Sep 2007 11:35:10 +0900
Message-ID: <46E8A1DE.8070907@w3.org>
To: ashok.malhotra@oracle.com
CC: public-ws-policy@w3.org

Added issue number for the record.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5045

Felix

ashok malhotra wrote:
>
> 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
Received on Thursday, 13 September 2007 02:35:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:38:36 UTC