System, method, and apparatus enabling effective and standardized methodology to represent JSON, XML, and XML Schema supporting transformation across formats and generate XML Schema for SaaS Applications
Publication Date: 2014-Jan-31
The IP.com Prior Art Database
Disclosed are a system, method, and apparatus for enabling an effective methodology to generate an Extensible Markup Language (XML) Schema from metadata provided by SaaS Applications using underlying standard intermediate schema Operation Data Transform (ODT). ODT can also contain data; this enables conversion of data from one form to another on the fly without pre-setup.
Page 01 of 3
and apparatus enabling effective and standardized methodology to
and apparatus enabling effective and standardized methodology to represent JSON ,
,, and XML Schema supporting transformation across formats
and XML Schema supporting transformation across formats and generate XML Schema for SaaS Applications
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
All the major data integration solutions represent the input and output for the SaaS
application offerings as XML Schema (XSD).
SaaS applications that expose web services provide an API to get all the members (i.e. metadata) of the required Object (e.g., Account, Opportunity etc.) in the custom format. Coming to ReST APIs, the applications expect either JSON or XML format data. Most
APIs expect JSON, given its many advantages; however, there is no such standard defined for JSON data. A provider exposing an API only mentions the sample JSON or
XML that can be used upon request.
A method is needed that allows data integration solutions to represent input and output in XSD format. One of the major issues is generating XSD from the metadata or sample JSON and XML provided by SaaS based applications.
In data integration solutions handling data in different formats (e.g., XML) JSON is troublesome. The transformation of JSON to XML and vice versa is a frequently faced scenario. For Example:
1. Given an orchestrated flow A-> B -> C
2. A and B activities pass the data in XML format to the next activity
3. In C , invoke a ReST API which expects data in JSON format
4. Perform a transformation from XML -> JSON
5. This transformed data is used for invoking the ReST API as part of C
Disclosed is a standardized and effective methodology to readily generate an input and output schema for an SaaS operation in data integration products using metadata, JSON, or XML from an SaaS provider. The methodology involves two parts:
1. Defining a standard intermediate schema representing an API's Request/Response metadata information provided by various SaaS providers
2. Generation of schema from the Operation Data Transform (ODT)
Figure: Components and Process
Page 02 of 3
Defining a standard intermediate schema representing an API's Request/Response metadata information provided by various SaaS providers Data accepted by the SaaS operation (e.g., web service or ReST API) is availa...