xacml — archive

RE: [xacml] Function Completeness

From: Polar Humenn <[email protected]>
To: [email protected]
Date: Wed, 18 Sep 2002 15:33:00 -0000

 MHonArc v2.5.2 -->

















xacml message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: RE: [xacml] Function Completeness




From: Polar Humenn <[email protected]>
To: Daniel Engovatov <[email protected]>
Date: Wed, 18 Sep 2002 15:31:51 -0400 (EDT)






On Wed, 18 Sep 2002, Daniel Engovatov wrote:

> >Do you really think it is not a good idea to cover that hole?
>
> This "hole", if any, is introduced by this new "higher-order" functions
> additions.

The MatchId specifies the boolean binary matching predicate you apply
between the explicit value and values returned by the designator. The
Match specifies the generic way in which you combine the results of each
comparison, which is "at least one must be true".

This semantics has been around longer than the higher-order function
specification.

Cheers,
-Polar

> Pardon me for repeating myself - but I already noted that for the target
> matching
> this functionality is fully redundant: euality based bag operations do
> provide all
> necessary functionality for urle indexing and selection, while condition is
> used for
> authorization decisions.  But this unneccessary additions already cause
> uncertainty
> and "holes".
>
> Daniel;
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>









References:

RE: [xacml] Function Completeness
From: Daniel Engovatov <[email protected]>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]


  









Powered by eList eXpress LLC