Rich,
Does the algorithm with your proposed changes lead to a different result
in any case than the algorithm which is in WD-19?
Best regards,
Erik
On 2011-05-17 15:36, rich levinson wrote:
> This is not a performance issue. It is a change from XACML 2.0 that
> implies
> that the combining algorithm has as input a set of decisions as
> opposed to 2.0
> where the combining algorithm had as input a set of Rules, Policies,
> or PolicySets,
> that had yet to be evaluated.
>
> The change implies that the algorithm is working on a different state,
> which is not
> the case.
>
> Thanks,
> Rich
>
>
> On 5/17/2011 5:07 AM, wrote:
>> From: Erik Rissanen [mailto:]
>> Sent: Tuesday, May 17, 2011 9:35 AM
>> To:
>> Subject: Re: [xacml] wd-19 indeterminate policy target handling
>>
>>> The spec should strive for the simplest possible explanation of the
>>> behavior, not the most efficient implementation.
>> +1 We can leave it up to vendors to come up with some nice
>> performance tricks.
>>
>> Thanks,
>> Ray
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail. Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
