The following examples show how to request the JUNOS configuration schema. In the NETCONF server’s response, the first <xsd:element> statement defines the <undocumented> JUNOS XML tag element, which can be enclosed in most other container tag elements defined in the schema (container tag elements are defined as <xsd:complexType>).
The attributes in several opening tags in the NETCONF server’s response appear on multiple lines for legibility only. The NETCONF server does not insert newline characters within tags or tag elements. Also, in actual output the JUNOS-version variable is replaced by a value such as 9.4R1 for the initial version of JUNOS Release 9.4.

Another <xsd:element> statement near the beginning of the schema defines the JUNOS XML <configuration> tag element. It encloses the <xsd:element> statement that defines the <system> tag element, which corresponds to the [edit system] hierarchy level. The statements corresponding to other hierarchy levels are omitted for brevity.
