Xml Comments; Xml Processing Instructions; Predefined Entity References - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

XML Comments

XML Processing Instructions

Predefined Entity References

12
must not depend on the presence or absence of white space in any particular location
when parsing the tag stream.
For more information about white space in XML documents, see the XML specification
from the World Wide Web Consortium (W3C), Extensible Markup Language (XML) 1.0,
at http://www.w3.org/TR/REC-xml/
Client applications and the Junos XML protocol server can insert XML comments at any
point between tag elements in the tag stream they generate, but not within tag elements.
Client applications must handle comments in output from the Junos XML protocol server
gracefully but must not depend on their content. Client applications also cannot use
comments to convey information to the Junos XML protocol server, because the server
automatically discards any comments it receives.
XML comments are enclosed within the strings
(two hyphens). For more details about comments, see the XML specification at
- -
http://www.w3.org/TR/REC-xml/
The following is an example of an XML comment:
<!- -This is a comment. Please ignore it. -->
An XML processing instruction (PI) contains information relevant to a particular protocol
and has the following form:
<?PI-name attributes?>
Some PIs emitted during a Junos XML protocol session include information that a client
application needs for correct operation. A prominent example is the
which the client application and Junos XML protocol server each emit at the beginning
of every Junos XML protocol session to specify which version of XML and which character
encoding scheme they are using. For more information, see "Emitting the <?xml?> PI"
on page 39 and "Parsing the Junos XML Protocol Server's <?xml?> PI" on page 41.
The Junos XML protocol server can also emit PIs that the client application does not need
to interpret (for example, PIs intended for the CLI). If the client application does not
understand a PI, it must treat the PI like a comment instead of exiting or generating an
error message.
By XML convention, there are two contexts in which certain characters cannot appear in
their regular form:
In the string that appears between opening and closing tags (the contents of the tag
element)
In the string value assigned to an attribute of an opening tag
When including a disallowed character in either context, client applications must
substitute the equivalent predefined entity reference, which is a string of characters that
.
<!-- and --> , and cannot contain the string
.
Copyright © 2010, Juniper Networks, Inc.
tag element,
<?xml?>