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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: RE: [xacml] Follow up on TC call


.. clarification for n.2 :  By implementing "callback" I meant that semantics of the extension functions changes from
"Get a list of argument values, return value", where value may be a sequence of primitive types, to
"Get a list of arguments and an operation name, invoke this arbitrary operation from the engine, return value of type determined by said operation."
..
-----Original Message-----
From: Daniel Engovatov [mailto:dengovatov@crosslogix.com]
Sent: Monday, September 16, 2002 9:41 AM
To: 'Simon Godik'; xacml@lists.oasis-open.org
Subject: [xacml] Follow up on TC call

2) Extensibility.  While it is true that supporting just the few "higher-order" predicates is not trouble some, including of the <function>, as a legal argument to any extension function complicates the development of proper extension interface.  For example take an extension function "all-greater" that takes an integer, sequence of integers and returns a Boolean.  If some policy requires it, this can be implemented as a library with a very simple interface - you pass in canonical representation of integer data type and it returns a canonical string representation of a Boolean value.   Implementing such extension with <function> passed to it will require an interface with "callback" functionality - to allow the extension to invoke an arbitrary other operation.  For multiple bindings it becomes troublesome.  But since such argument is allowed - it has to be be implemented..
 
 


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


Powered by eList eXpress LLC