RE: [xacml] change request: xacml context attributes and data typ es

I would agree with his suggestion of keeping the dataType.  I would also like to point out his concern that "it requires an API that is more complex (for extending the engine to support custom functions)"  I have noticed the same issue.  It is even more pronounced with the "higher-order" functions, with their current syntax.  BTW - was their any discussion on MIchiharu's proposal on their extensibility?