RE: [xacml] Extension of higher-order bag function

[Daniel Engovatov <dengovatov@crosslogix.com>]

I would strongly second that.  Here is my proposal.

1) Change the syntax of the higher-order application to use an attribute to
<apply>, rather then a function-type argument.  It will look like this:

<Apply base="higher-order-base:any-of-all"
FunctionId="function:integer-greater">
<..>

or for the map

<Apply base="higher-order-base:map"
FuncitonId="function:integer-to-decimal"> 
...


2) Base (or whatever other name) - attribute is made a separate extension
point - of type QName, so other
higher order algorithms, for example a very useful "bind2nd","bind1st"
operations can be introduced.

3) This syntax highlights the fact that it is the FunctionId designated
funtion is being applied.
Restrictions in <Match> become clearer.

4) Simple function extension interface is preserved - no "function", as data
type.


Daniel.


-----Original Message-----
From: Michiharu Kudoh [mailto:KUDO@jp.ibm.com]
Sent: Monday, September 23, 2002 7:04 AM
To: XACML
Subject: [xacml] Extension of higher-order bag function


I am wondering whether or not XACML allows policy writer to extend
higher-order bag functions. Since current set support sufficient operations
on bag(s), how about disallowing to extend higher-order bag functions (at
least at ver 1.0)?  It makes things simpler.

Michiharu Kudo

IBM Tokyo Research Laboratory, Internet Technology
Tel. +81 (46) 215-4642   Fax +81 (46) 273-7428





----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>