I have my own functions and datatypes - hence I find it counter
intutive. I do agree that a standard mechanism (functions, etc) cannot
fathom an arbitrary structure in an attributevalue - but I would have
thought that if I define my own functions and own datatypes then I
should be able to process it - even with a standard implementation.
prakash
On Wed, 9 Mar 2005 09:50:57 -0800, Daniel Engovatov <> wrote:
>
> >This seems counter intutive to me in that the schema is open enough to
> >allow embedding my own structure into the AttributeValue but I cannot
> >leverage it in a meaningful manner in the AttributeSelector.
>
> Why counter intuitive? You can only use context data as an argument
> for a function used within the condition. XACML standard functions do
> not use any custom data types that you may import from your schema or
> from other applications, so you can not use them in a standard XACML
> expression.
>
> Daniel;
>
>
