[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 10 September, Polar Humenn writes: Re: [xacml] [CR#37] Add normalized-string-match function > > 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? From http://www.columbia.edu/kermit/utf8.html: UTF-8 is an ASCII-preserving encoding method for Unicode (ISO 10646), the Universal Character Set (UCS). The UCS encodes most of the world's writing systems in a single character set, allowing you to mix languages and scripts within a document without needing any tricks for switching character sets. This web page is encoded directly in UTF-8. So, if I understand correctly, since we specify UTF8 as our encoding, a RequestContext in Unicode and a Policy in ASCII will compare nicely. Anne -- Anne H. Anderson Email: Anne.Anderson@Sun.COM Sun Microsystems Laboratories 1 Network Drive,UBUR02-311 Tel: 781/442-0928 Burlington, MA 01803-0902 USA Fax: 781/442-1692
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC