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

1. A computer-implementable method for performing a data content mapping operation, comprising:

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.

2. The method of claim 1 , wherein:

the identifying the plurality of components within the first document comprises identifying a structure of the first document.

3. The method of claim 2 , wherein:

the node path representation comprises identified node paths and node types; and,

the identified node paths and node types are used to generate an associated document node path listing for the first document.

4. The method of claim 3 , further comprising:

identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document.

5. The method of claim 4 , further comprising:

replacing each of the leaf nodes with a respective link in the parent nodes.

6. The method of claim 1 , further comprising:

receiving a second document from the product supplier;

determining whether the second document conforms to the first data schema;

identifying differences between the first document and the second document; and

mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema.

7. 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.

8. The system of claim 7 , wherein:

the identifying the plurality of components within the first document comprises identifying a structure of the first document.

9. The system of claim 8 , wherein:

the node path representation comprises identified node paths and node types; and,

the identified node paths and node types are used to generate an associated document node path listing for the first document.

10. The system of claim 9 , wherein the instructions executable by the processor are further configured for:

identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document.

11. The system of claim 10 , wherein the instructions executable by the processor are further configured for:

replacing each of the leaf nodes with a respective link in the parent nodes.

12. The system of claim 7 , wherein the instructions executable by the processor are further configured for:

receiving a second document from the product supplier;

determining whether the second document conforms to the first data schema;

identifying differences between the first document and the second document; and

mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema.

13. 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.

14. The non-transitory, computer-readable storage medium of claim 13 , wherein:

the identifying the plurality of components within the first document comprises identifying a structure of the first document.

15. The non-transitory, computer-readable storage medium of claim 14 , wherein:

the node path representation comprises identified node paths and node types; and,

the identified node paths and node types are used to generate an associated document node path listing for the first document.

16. The non-transitory, computer-readable storage medium of claim 15 , wherein the computer executable instructions are further configured for:

identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document.

17. The non-transitory, computer-readable storage medium of claim 16 , wherein the computer executable instructions are further configured for:

replacing each of the leaf nodes with a respective link in the parent nodes.

18. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are further configured for:

receiving a second document from the product supplier;

determining whether the second document conforms to the first data schema;

identifying differences between the first document and the second document; and

mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema.

19. The non-transitory, computer-readable storage medium of claim 13 , wherein:

the computer executable instructions are deployable to a client system from a server system at a remote location.

20. The non-transitory, computer-readable storage medium of claim 13 , wherein:

the computer executable instructions are provided by a service provider to a user on an on-demand basis.