[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [xacml] change request: xacml context attributes and data types
my point is that they *are* strings. for them to become specific data types you will have to perform real-time type validation; an operational point i know, but what would be the benefit of doing it this way? maybe i am missing something important here, but it seems that implied validation (validation during rule 'compilation', string comparison only thereafter) would be a whole heck of a lot more efficient. b Simon Godik wrote: > Polar, > I assume we have x500Name data type and rfc822Name data type. > (At least those types are mentioned in the current draft). > In other words, they are not merely strings. > In this case, in your example there is type conversion error > and result would be inderteminate. > Simon
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC