OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xacml-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [xacml-comment] C003 and matching in targets and conditions

On Fri, 22 Nov 2002, John Merrells wrote:

> It's suddenly dawned on me that the signature of the match functions
> is supposed to differ between targets and conditions. In a condition
> it's (primitive, primitive) and in a target it's (primitive,
> bag<primitive>).
> Is this intentional? It seems like a mistake to me. It'd be much simpler
> for everyone if the signature wasn't dependent upon the context...

It is not a mistake. The *Match constructs take the match function and
apply it between each element in the bag and the explicit value.

Currently, the equivalent expression to a Match element that would appear
in the condition as:

( any-of matchId-function primitive bag<primitive> ).


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC