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

[Bug 5045] Why did intersection fail?

From: <bugzilla@wiggum.w3.org>
Date: Wed, 12 Sep 2007 21:43:13 +0000
CC:
To: public-ws-policy-qa@w3.org
Message-Id: <E1IVZzN-0002x8-6H@wiggum.w3.org>

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

           Summary: Why did intersection fail?
           Product: WS-Policy
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Framework
        AssignedTo: fsasaki@w3.org
        ReportedBy: ashok.malhotra@oracle.com
         QAContact: public-ws-policy-qa@w3.org


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 Wednesday, 12 September 2007 21:43:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:09 GMT