US Patent Application 17726781. Methods Make Web and Business Application Data Access Agnostic to Schema Variations and Migrations simplified abstract
Contents
Methods Make Web and Business Application Data Access Agnostic to Schema Variations and Migrations
Organization Name
Inventor(s)
Ching-Yun Chao of Austin TX (US)
Steve Petrucci of Bellevue WA (US)
Methods Make Web and Business Application Data Access Agnostic to Schema Variations and Migrations - A simplified explanation of the abstract
- This abstract for appeared for US patent application number 17726781 Titled 'Methods Make Web and Business Application Data Access Agnostic to Schema Variations and Migrations'
Simplified Explanation
This abstract describes a system, method, and computer-readable medium for performing a data schema mapping operation. The operation involves receiving product information from a product supplier, which is in the form of a document following a specific data schema called the first data schema. The first data schema is in an unspecified JavaScript Object Notation (JSON) format.
The system then identifies various components within this document, which are essentially JSON data elements. It also identifies a second set of components that adhere to a different data schema called the second data schema. This second data schema is a defined schema and is associated with a data center services provider. Some of the components in the second set are associated with a relational database.
Finally, the system maps a component from the document following the first data schema to a corresponding component in the second data schema. This mapping allows for the integration and synchronization of data between different schemas, facilitating data management and analysis.
Original Abstract Submitted
A system, method, and computer-readable medium are disclosed for performing a data schema mapping operation. The data schema mapping operation includes receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a data center services provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema.
