[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml-comment] Definition of string-equal
I would be strongly opposed to "implemntation-defined" due policy interop issues. Can we utilize 'ecncoding' attribute somehow that is coming in XML request instead? E.g. if encoding="utf-8" in request then all strings should be interpreted and compared as UTF-8 encoded strings. --- On Wed, 8/6/08, Roland Illig <roland.illig@gmx.de> wrote: > From: Roland Illig <roland.illig@gmx.de> > Subject: [xacml-comment] Definition of string-equal > To: xacml-comment@lists.oasis-open.org > Date: Wednesday, August 6, 2008, 5:55 PM > Hi, > > why do the XACML documents specify that the string-equal > function > compares strings byte-by-byte? In XMLSchema, strings are > defined as > sequences of _characters_, not of bytes. Which encoding > shall be used > for converting strings to bytes, or is this > implementation-defined? > > Roland > > -- > This publicly archived list offers a means to provide input > to the > OASIS eXtensible Access Control Markup Language (XACML) TC. > > In order to verify user consent to the Feedback License > terms and > to minimize spam in the list archive, subscription is > required > before posting. > > Subscribe: xacml-comment-subscribe@lists.oasis-open.org > Unsubscribe: xacml-comment-unsubscribe@lists.oasis-open.org > List help: xacml-comment-help@lists.oasis-open.org > List archive: > http://lists.oasis-open.org/archives/xacml-comment/ > Feedback License: > http://www.oasis-open.org/who/ipr/feedback_license.pdf > List Guidelines: > http://www.oasis-open.org/maillists/guidelines.php > Committee: > http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]