xacml — archive

Re: [xacml] legal values for Strings

From: Seth Proctor <[email protected]>
To: [email protected]
Date: Fri, 26 Mar 2004 17:13:00 -0000

 MHonArc v2.5.0b2 -->

xacml message

[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]

Subject: Re: [xacml] legal values for Strings

From: Seth Proctor <[email protected]>
To: Polar Humenn <[email protected]>
Date: Fri, 26 Mar 2004 12:27:53 -0500

On Thu, 2004-03-25 at 08:41, Polar Humenn wrote:
> The string may contain any kind of characters as it wants. It may also
> contain "42".
> 
> Conceivably, I should be able to have
> 
>    <AttributeValue DataType="...:string" AttributeId="foo">
>      <bar>baz
>    </AttributeValue>
> 
> Would that cause a problem with the current DOM parsers?

Yes, it would. The problem with the example you give here is that it's
not valid XML. If you use some common system like DOM or SAX to parse
your XML, then this example should be rejected before you ever get the
chance to work with it.

> Do we need a new string type that that "escapes" tag brackets?
> 
> For example:
>    <AttributeValue DataType="...:string" AttributeId="foo">
>      \<bar>baz\</bar>
>    </AttributeValue>
> 
> But then that means we must also escape the escape (i.e. "\\").

As Daniel and others have pointed out, there actually already is an
escaping machanism in XML for bracket characters. Convenient eh? :) This
means that you can express your example in a valid form without having
to come up with a new escaping mechanism. It also means that we don't
need to define a new string datatype. At least, this is how some of us
are reading it.

seth

References:

legal values for Strings
From: Seth Proctor <[email protected]>
Re: [xacml] legal values for Strings
From: Polar Humenn <[email protected]>

[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]