xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [xacml] [CR#37] Add normalized-string-match function
MHonArc v2.5.2 -->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
- From: Polar Humenn <[email protected]>
- To: Anne Anderson <[email protected]>
- Date: Tue, 10 Sep 2002 13:56:39 -0400 (EDT)
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
- Follow-Ups:
- Re: [xacml] [CR#37] Add normalized-string-match function
- From: Anne Anderson <[email protected]>
- Re: [xacml] [CR#37] Add normalized-string-match function
- References:
- [xacml] [CR#37] Add normalized-string-match function
- From: Anne Anderson <[email protected]>
- [xacml] [CR#37] Add normalized-string-match function
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]