AUTOMATIC MAP UPDATING BASED ON SCHEMA CHANGES

• US 20080168109A1
• Filed: 01/09/2007
• Published: 07/10/2008
• Est. Priority Date: 01/09/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gaurav, Suraj, Machiraju, Surendra
• Application Number:
  US11/621,372
• Publication Number:
  US 20080168109A1
• Time in Patent Office: Days
• US Class Current: 707/203
• CPC Class Codes: G06F 16/213 with details for schema evolution support

Abstract

Systems and methods for automatic updating of maps based on changes to underlying schema is provided. Schema maps are automatically updated based on changes in underlying schema, such as TSDs of an EDI system. A versioning mechanism also versions the schema maps as they evolve over time, so that changes in the schema maps can be understood commensurate with the changes in the underlying schema. A tool is also provided that allows a user to interface with different versions of schema maps and underlying schema, enabling a visual understanding to understand the evolution of any schema map and the underlying schema. Moreover, the tool allows manual changes to the underlying schema, which in turn results in automatic updating of the affected map(s).

Claims

1. A method, comprising:

receiving information representative of at least one change to a schema of a plurality of schema in a computing system; and

in response to receiving the information, automatically updating at least one dependent entity of a plurality of dependent entities in the computing system that depend from the at least one change to the schema, each of which plurality of dependent entities is based on at least one schema of the plurality of schema.

2. The method of claim 1, wherein the at least one dependent entity of the plurality of dependent entities includes at least one map of a plurality of maps, each of which interrelates at least two schema of the plurality of schema.

3. The method of claim 2, wherein said updating includes storing versioning information for the at least one map.

4. The method of claim 3, further including:

displaying a map of the at least one map and based on the versioning information, displaying changes made to the map from the automatically updating step.

5. The method of claim 1, wherein said updating includes updating interrelationships between structural elements of at least two schema of the plurality of schema.

6. The method of claim 1, further including:

editing a schema of the plurality of schema via an editing tool; and

wherein said receiving includes receiving an output of said editing indicative of any changes effected during said editing.

7. The method of claim 1, wherein said receiving includes receiving information representative of at least one change to at least one Electronic Data Interchange (EDI) transaction set definition (TSD) of an EDI messaging system.

8. The method of claim 1, wherein said receiving includes receiving information representative of at least one change to at least one relational database table structure definition of a relational database system.

9. The method of claim 1, wherein said receiving includes receiving information representative of at least one change to at least one RosettaNet schema definition of a RosettaNet communications system.

10. A computer readable medium comprising computer executable instructions for performing the method of claim 1.

11. A server object for interfacing with at least one data store that stores a plurality of schema as a plurality of schema elements and a plurality of schema maps that define mappings between the plurality of schema elements of different schema of the plurality of schema, including:

a schema map update component that receives a representation of at least one schema change made to at least one schema element of at least one schema of the plurality of schema from the at least one data store, and automatically updates at least one schema map that is dependent upon the at least one schema change; and

an interface component for interfacing to the at least one data store on behalf of the schema map update component to receive said representation of the at least one schema change and to store said updated at least one schema map.

12. The server object of claim 11, wherein the schema map update component determines versioning information for the at least one map, wherein the versioning information enables differences between different versions of a map to be determined.

13. The server object of claim 11, further including:

a user interface component for displaying at least one schema of the plurality of schema.

14. The server object of claim 13, wherein said user interface component is further for editing at least one schema of the plurality of schema to generate said at least one schema change.

15. The server object of claim 11, further including:

a user interface component for displaying the updated at least one schema map.

16. A method for use in an electronic data interchange (EDI) communications system, comprising:

receiving change data representing at least one change to at least one transaction set definition (TSD) of the EDI system; and

in response to receiving the change data, automatically updating mappings represented by at least one map that is based on the at least one changed TSD, wherein the mappings interrelate EDI elements of at least two TSDs.

17. The method of claim 16, wherein said updating includes storing versioning data for the at least one map wherein the versioning data represents differences between different versions of a map after said updating.

18. The method of claim 17, further including:

displaying a map of the at least one map and based on the versioning information, displaying changes made to the map from the automatically updating step.

19. The method of claim 16, further including:

editing a TSD of the at least one TSD via an editing tool; and

wherein said receiving includes receiving change data representing changes made to the TSD during said editing.

20. The method of claim 16, further including:

determining whether any maps are dependent on the at least one changed TSD, and if so, performing said automatic updating step.