That's what we need function declaration syntax for..
The problem is - you may have a correct input type, but still get an error,
that has to be communicated in a generic way. For example
account_balance(subject::account_id) may return INdeterminate for an invalid
account Id or for a failed query. There is no easy way to validate that all
account_id used are valid before the evaluation - you would not want to
embed any cutom validation logic into your engine, would not you?
-----Original Message-----
From: Anne Anderson [mailto:]
Sent: Wednesday, December 04, 2002 10:51 AM
To: 'XACML TC '
Subject: Re: [xacml] IIC012: syntax-error or processing-error?
Polar,
How do you handle the type-correctness checking in the case of
custom functions? Do all custom functions have to be hardwired
into your XACML evaluation engine? If not, and you have a
pluggable interface, is there some method to query for the types
of the arguments that a given function expects? Or what?
Anne
--
Anne H. Anderson Email:
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311 Tel: 781/442-0928
Burlington, MA 01803-0902 USA Fax: 781/442-1692
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
