Browse Prior Art Database

System and method to convert json to complex xml structures Disclosure Number: IPCOM000243761D
Publication Date: 2015-Oct-16
Document File: 7 page(s) / 170K

Publishing Venue

The Prior Art Database


Software as a Service (SaaS) based applications are becoming more popular. Enterprises are eager to use Customer Relationship Management (CRM) and Enterprise Resource Planning (ERP) applications/solutions. Such applications expose web services and/or Representational State Transfer (ReST) based Application Protocol Interfaces (APIs), which expect Simple Object Access Protocol (SOAP) message, JavaScript* Object Notation (JSON) or Extensible Markup Language (XML) as input, respectively. To communicate with one another, computers use various protocols and message formats. A system is able to interpret messages in formats for which the system includes an appropriate serialization stack used to convert the message to usable application data or objects. XML is efficient at describing and defining data and is therefore used ever increasingly in data intensive applications. XML allows users to define schemas comprising a set of elements and attributes in a structural relationship to define a non-programming language specific data type (i.e. a data type that is defined without use of particular programming language). Alternatively, a text-based dynamic language designed for human-readable data interchange, such as JavaScript Object Notation (JSON) may be used as a format for sending data. JSON is a language independent data format. The solution proposes a way to convert json to complex xml structures.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 7

System and method to convert json to complex xml structures

Each of these formats is interpreted by different incompatible serialization stacks. Some of the difficulty in interchanging XML and JSON arises from different format requirements.

XML documents are used to provide data to applications that perform various operations using the XML data. Commonly, such applications are configured to receive the XML data in a given order and having a specified format. If the data is provided in an incorrect order or having an improper format, it may be unusable by an application. Improperly configured XML data can cause application programs to fail or crash or cause other undesirable outcomes. Under such circumstances the XML document (and associated data) are considered "invalid".

XML messages always include a root name, have namespace for each of the complex types, whereas some dynamic languages, such as JSON, do not include a root name. JSON is built on 2 structures - a collection of name/value pairs and an ordered list of values.

Further difficulties can arise during parsing, validating and transformation of JSON data to XML as the converted XML will not confirm to the schema/standard expected by the next consuming application. Also the JSON data does not need a root name but the XML always needs a root name. The consuming applications have to perform extra processing to convert the xml to the format xml which their target application needs.

Figure 1: Sample JSON to XML Conversion

All the conventional tools and systems available converts the json to a default xml only.

The present invention discloses a system and method to convert json to xml...