Methods make web and business application data access agnostic to schema variations and migrations

A system comprising:

• a processor;
• a data bus coupled to the processor;
• and
• a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for:
• 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 a unspecified JavaScript Object Notation (JSON) schema, the unspecified JSON schema comprising a data schema having an undefined format, the undefined format being undefined by a recipient of a document conforming to the unspecified 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, the identifying comprising constructing a node path representation of the plurality of components within the first document;
• 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 services provider, the defined data schema comprising a data schema conforming to a defined format, the defined format being prescribed by the service 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.

A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for:

• 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, the unspecified JSON schema comprising a data schema having an undefined format, the undefined format being undefined by a recipient of a document conforming to the unspecified 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, the identifying comprising constructing a node path representation of the plurality of components within the first document;
• 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 services provider, the defined data schema comprising a data schema conforming to a defined format, the defined format being prescribed by the service 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.