<rpc-reply xmlns:junos="URL">
<operational-response xmlns="URL-for-DTD">
<!- - JUNOS XML tag elements for the requested operational data - ->
</operational-response>
</rpc-reply>
<rpc-reply xmlns:junos="URL">
<configuration xmlns="URL" junos:(changed | commit)-seconds="seconds" \
junos:(changed | commit)-localtime="YYY-MM-DD hh:mm:ss TZ" \
[junos:commit-user="username"]>
<!- - JUNOS XML tag elements for the requested configuration data - ->
</configuration>
</rpc-reply>
For operational responses, define the XML namespace for the enclosed tag elements that do not have a prefix (such as junos:) in their names. The namespace indicates which JUNOS XML document type definition (DTD) defines the set of tag elements in the response.
For configuration data responses, define the XML namespace for the enclosed tag elements.
See Requesting Operational Information and Requesting Information from the Committed or Candidate Configuration.
<configuration> in the JUNOS XML API Configuration Reference, <rpc-reply>, junos:changed-localtime, junos:changed-seconds, junos:commit-user, junos:commit-localtime, junos:commit-seconds