XML and NETCONF Tag Elements

Items in an XML-compliant document or data set are always enclosed in paired opening and closing tags. XML is stricter in this respect than HTML, which sometimes uses only opening tags. The following examples show paired opening and closing tags enclosing a value:

The term tag element refers to the triple of opening tag, contents, and closing tag. The content can be an alphanumeric character string as in the preceding examples, or can itself be a container tag element, which contains other tag elements.

If a tag element is empty—has no contents—it can be represented either as paired opening and closing tags with nothing between them, or as a single tag with a forward slash after the tag name. For example, the notation <eventing/> is equivalent to <eventing></eventing>.

As the preceding examples show, angle brackets enclose the name of a NETCONF or SRC XML tag element in its opening and closing tags. This is an XML convention, and the brackets are a required part of the complete tag element name. They are not to be confused with the angle brackets used in Juniper Networks documentation to indicate optional parts of CLI command strings.

NETCONF and SRC XML tag elements obey the XML convention that the tag element name indicates the kind of information enclosed by the tag element. For example, the name of the SRC XML <interface> tag element indicates that it contains information about an interface on the C-series Controller, whereas the name of the <name> tag element indicates that its contents specify the identifier.

When discussing tag elements in text, the convention is to use just the name of the opening tag to represent the complete tag element (opening tag, contents, and closing tag). For example, it usually refers to “the <interface> tag element” instead of “the <interface><name>name </name></interface> tag element.”

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.