Table 3: Predefined Entity Reference Substitutions For Tag Content Values; Table 4: Predefined Entity Reference Substitutions For Attribute Values - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Copyright © 2010, Juniper Networks, Inc.
Chapter 2: Using Junos XML Management Protocol and Junos XML Tag Elements
represents the disallowed character. Because the Junos XML protocol server uses the
same predefined entity references in its response tag elements, the client application
must be able to convert them to actual characters when processing response tag
elements.
Table 3 on page 13 summarizes the mapping between disallowed characters and
predefined entity references for strings that appear between the opening and closing
tags of a tag element.

Table 3: Predefined Entity Reference Substitutions for Tag Content Values

Disallowed Character
& (ampersand)
> (greater-than sign)
< (less-than sign)
Table 4 on page 13 summarizes the mapping between disallowed characters and
predefined entity references for attribute values.

Table 4: Predefined Entity Reference Substitutions for Attribute Values

Disallowed Character
(ampersand)
&
(apostrophe)
'
> (greater-than sign)
>
(less-than sign)
<
(quotation mark)
"
As an example, suppose that the following string is the value contained by the
tag element:
if (a<b && b>c) return "Peer's not responding"
The <condition> tag element looks like this (it appears on two lines for legibility only):
<condition>if (a&lt;b &amp;&amp; b&gt;c) return "Peer's not \
responding"</condition>
Similarly, if the value for the
Peer's "age" <> 40 , the opening tag looks like this:
<example heading="Peer&apos;s &quot;age&quot; &lt;&gt; 40">
Predefined Entity
Reference
&amp;
&gt;
&lt;
Predefined Entity
Reference
&amp;
&apos;
&gt;
&lt;
&quot;
tag element's
<example>
<condition>
attribute is
heading
13