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] [CR#37] Add normalized-string-match function


On Tue, 10 Sep 2002, Anne Anderson wrote:

> This CR proposes to define string-equal as "xf:compare(arg1,arg2)
> == 0", with a default collation (Unicode collation algorithm) of
> "comparison on each character of the string using integer-equal".
>
> I would like to suggest that we not support any other "collation
> algorithms" for string-equal, and not even reference xf:compare
> in the definition for string-equal.
>
> Define string-equal as 'the two arguments, when compared
> byte-by-byte using "integer-equal", exactly match'.

Is that byte-by-byte the way it appears in the XML documents? What would
that mean if the Policy was in ASCII and the RequestContext is in Unicode?

-Polar





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


Powered by eList eXpress LLC