MHonArc v2.5.0b2 -->
















xacml message






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

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [xacml] URI match function




From: Tim Moses <tim.moses@entrust.com>
To: "'Michiharu Kudoh'" <KUDO@jp.ibm.com>,       "'xacml'" <xacml@lists.oasis-open.org>
Date: Tue, 15 Jun 2004 11:24:30 -0400






Michiharu - Thanks for your comment.

I chose the name url-match over uri-match because the function does not
address urns, only urls.

I agree with your interpretation of the function as expressed in your table.

I agree with your idea of being able to match either all descendants or just
children.

There appear to be a number of possible ways to achieve this, and a little
discussion would probably be worthwhile.

We could have two functions, as you propose, or we could have a new reserved
character, as (I think) Bill is proposing.  If we expect policy writers to
use the two options interchangeably in a policy, then expressing the
distinction in the argument (i.e. using a new reserved character) seems
preferable to expressing it in the function name.

Why don't we discuss at our next focus group meeting?

All the best.  Tim.