Complying with XML and NETCONF Conventions

A client application must comply with XML and NETCONF conventions. Each request from the client application must be a well-formed XML document; that is, it must obey the structural rules defined in the NETCONF and JUNOS XML DTDs for the kind of information encoded in the request. The client application must emit tag elements in the required order and only in the legal contexts. Compliant applications are easier to maintain in the event of changes to the JUNOS software or NETCONF API.

Similarly, each response from the NETCONF server constitutes a well-formed XML document (the NETCONF server obeys XML and NETCONF conventions). The following sections describe NETCONF conventions:

• Request and Response Tag Elements
• Child Tag Elements of a Request Tag Element
• Child Tag Elements of a Response Tag Element
• Spaces, Newline Characters, and Other White Space
• XML Comments
• Predefined Entity References

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