GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
JSON2XML(1) pyang manual JSON2XML(1)

json2xml - translates JSON documents conforming to a YANG data model into XML.

json2xml [-t target] [-o output_file] driver_file json_file

json2xml -h | --help

This program translates json_file into XML using the procedure specified in RFC 7951[1].

The translation uses a second input file, driver_file, which contains a concise JSON representation of the YANG data model to which json_file should conform, at least structurally. Normally, driver_file is obtained as the jtox output of pyang.

Using "-" (hyphen) in place of json_file instructs the program to read a JSON document from the standard input.

The target argument specifies the document (root) element for the output XML document. This encapsulation is necessary because the input JSON document may contain multiple JSON objects at the top level. Supported values for the target argument are:

data

The document element will be <nc:data>. This is the default.

config

The document element will be <nc:data>.

The XML prefix "nc" represents the standard NETCONF namespace with URI "urn:ietf:params:xml:ns:netconf:base:1.0".

-t target, --target target
Specifies the target type of the output XML document, i.e. its document element. The default is data.

-o output_file, --output output_file

Write output to output_file instead of the standard output.

-h, --help

Displays help screen and exits.

$ pyang -f jtox -o dhcp.jtox dhcp.yang

$ json2xml -o dhcp-data.xml dhcp.jtox dhcp-data.json

The first command generates the driver file dhcp.jtox, which is then used for translating JSON file dhcp-data.json to XML file dhcp-data.xml.

json2xml return codes have the following meaning:

0

No error (normal termination)

1

One of the input files cannot be read

2

Error in command line arguments

3

JSON to XML translation failed

RFC 7951[1], pyang(1), JSON[2].

Ladislav Lhotka <lhotka@nic.cz>
CZ.NIC

1.
RFC 7951
http://tools.ietf.org/html/rfc7951
2.
JSON
http://www.json.org/
2019-01-21 json2xml-1.7.8

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.