IP Library › Granted Patent US 7,877,421

Granted Patent B2

US 7,877,421 · App. 10/637,339 · Granted Jan 25, 2011

Method and system for mapping enterprise data assets to a semantic information model

Assignee: International Business Machines Corporation

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 7,877,421
App. No.: 10/637,339
Granted: Jan 25, 2011
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

A method for mapping data schemas into an ontology model, including providing an ontology model including classes and properties of classes, providing a data schema, identifying a primary data construct within the data schema, identifying a secondary data construct within the primary data construct, mapping the primary data construct to a corresponding class of the ontology model, and mapping the secondary data construct to a property of the corresponding class of the ontology model. A system and a computer readable storage medium are also described and claimed.

Claims (260)

1. A method executed in a computer for deriving a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the method comprising:

providing an ontology model including classes and properties of classes;

providing the source data schema;

providing the target data schema, wherein the target data schema is different from the source data schema;

identifying a first primary data construct within the source data schema;

identifying a first secondary data construct within the first primary data construct;

identifying a second primary data construct within the target data schema;

identifying a second secondary data construct within the second primary data construct;

generating a first mapping for mapping the first primary data construct to a corresponding class of the ontology model;

generating a second mapping for mapping the first secondary data construct to a property of the corresponding class of the ontology model;

generating a third mapping for mapping the second primary data to a corresponding class of the ontology model;

generating a fourth mapping for mapping the second secondary data construct to a property of the corresponding class of the ontology model; and

deriving the transformation, wherein the transformation is based on the first mapping, the second mapping, the third mapping, and the fourth mapping.

2. The method of claim 1 wherein the ontology model includes a generic industry model.

3. The method of claim 1 wherein the ontology model includes an enterprise specific model.

4. The method of claim 1 wherein the ontology model includes business rules that relate properties of a class.

5. The method of claim 4 wherein the business rules include conversion rules, for converting among properties of a class.

6. The method of claim 1 wherein the ontology model is a distributed model.

7. The method of claim 1 wherein the source data schema is specified by a meta-model that describes the first primary data construct and the first secondary data construct.

8. The method of claim 1 wherein the first mapping and the second mapping are generated manually by a user.

9. The method of claim 1 wherein generating the first mapping and generating the second mapping are performed automatically, based on matching at least partial names between the primary data construct and a class of the ontology model, and between the secondary data construct and a property of the class, respectively.

10. The method of claim 1 wherein generating the first mapping and generating the second mapping are performed automatically, based on matching at least partial names between the primary data construct and another primary data construct for which said mapping the primary data construct has already been performed, and between the secondary data construct and another secondary data construct for which said mapping the secondary data construct has already been performed, respectively.

11. The method of claim 1 wherein the second mapping is performed automatically based on matching data types between the secondary data construct and a property of the corresponding class.

12. The method of claim 1 wherein the first mapping and the second mapping use a Resource Description Framework (RDF) expression.

13. The method of claim 1 wherein said providing, identifying a primary data construct, and identifying a secondary data construct are enabled through an application programming interface (API).

14. The method of claim 1 wherein said providing, identifying a primary data construct, and identifying a secondary data construct are enabled through a graphical user interface (GUI).

15. The method of claim 1 further comprising calculating statistics for the ontology model.

16. The method of claim 1 further comprising calculating statistics for the source data schema.

17. The method of claim 16 wherein the statistics for the source data schema include the number of primary data constructs within the source data schema that have been mapped to corresponding classes of the ontology model.

18. The method of claim 16 wherein the statistics for the source data schema include the number of secondary data constructs within the data schema that have been mapped to corresponding properties of the ontology model.

19. The method of claim 16 wherein the statistics for the source data schema include the percentage of primary data constructs within the source data schema that have been mapped to corresponding classes of the ontology model.

20. The method of claim 16 wherein the statistics for the source data schema include the percentage of secondary data constructs within the source data schema that have been mapped to corresponding properties of the ontology model.

21. A method executed in a computer for deriving a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the method comprising:

providing an ontology model including classes and properties of classes, each property having associated therewith a target class;

providing the source data schema;

providing the target data schema, wherein the target data schema is different from the source data schema;

identifying a first primary data construct within the source data schema;

identifying a first secondary data construct within the first primary data construct;

identifying a second primary data construct within the target data schema;

identifying a second secondary data construct within the second primary data construct;

generating a first mapping for mapping the first primary data construct to a corresponding class of the ontology model;

generating a second mapping for mapping the first secondary data construct to an inverse of a property whose target class is the corresponding class of the ontology model;

generating a third mapping for mapping the second primary data construct to a corresponding class of the ontology model;

generating a fourth mapping for mapping the second secondary data construct to an inverse of a property whose target class is the corresponding class of the ontology model; and

deriving the transformation from data conforming with the source data schema into data conforming with the target data schema, wherein the transformation is based on the first mapping, the second mapping, the third mapping, and the fourth mapping.

22. A method executed in a computer for deriving a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the method comprising:

providing an ontology model including classes and properties of classes, and including inheritance relationships for superclasses;

providing the source data schema;

providing the target data schema, wherein the target data schema is different from the source data schema;

identifying a first primary data construct within the source data schema;

identifying a first secondary data construct within the first primary data construct;

identifying a second primary data construct within the target data schema;

identifying a second secondary data construct within the second primary data construct;

generating a first mapping for mapping the first primary data construct to a corresponding class of the ontology model;

generating a second mapping for mapping the first secondary data construct to a property of a superclass of the corresponding class of the ontology model;

generating a third mapping for mapping the second primary data construct to a corresponding class of the ontology model;

generating a fourth mapping for mapping the second secondary data construct to a property of a superclass of the corresponding class of the ontology model; and

deriving the transformation, wherein the transformation is based on the first mapping, the second mapping, the third mapping, and the fourth mapping.

23. A method executed in a computer for deriving a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the method comprising:

providing an ontology model including classes and properties of classes, and including inheritance relationships for superclasses;

providing the source data schema;

providing the target data schema, wherein the target data schema is different from the source data schema;

identifying a first primary data construct within the source data schema;

identifying a first secondary data construct within the first primary data construct;

identifying a second primary data construct within the target data schema;

identifying a second secondary data construct within the second primary data construct;

generating a first mapping for mapping the first primary data construct to a corresponding class of the ontology model;

generating a second mapping for mapping the first secondary data construct to an inverse of a property whose target class is a superclass of the corresponding class of the ontology model;

generating a third mapping for mapping the second primary data construct to a corresponding class of the ontology model;

generating a fourth mapping for mapping the second secondary data construct to an inverse of a property whose target class is a superclass of the corresponding class of the ontology model; and

deriving the transformation, wherein the transformation is based on the first mapping, the second mapping, the third mapping, and the fourth mapping.

24. A method executed in a computer for deriving a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the method comprising:

providing an ontology model including classes and properties of classes;

providing the source data schema;

providing the target data schema, wherein the target data schema is different from the source data schema;

identifying a first primary data construct within the source data schema;

identifying a first secondary data construct within the first primary data construct;

identifying a second primary data construct within the target data schema;

identifying a second secondary data construct within the second primary data construct;

generating a first mapping for mapping the first primary data construct to a corresponding class of the ontology model;

generating a second mapping for mapping the first secondary data construct to a composition of properties, one of which is a property of the corresponding class of the ontology model;

generating a third mapping for mapping the second primary data construct to a corresponding class of the ontology model;

generating a fourth mapping for mapping the second secondary data construct to a composition of properties, one of which is a property of the corresponding class of the ontology model; and

deriving the transformation, wherein the transformation is based on the first mapping, the second mapping, the third mapping, and the fourth mapping.

25. A system for generating a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the system comprising:

a memory for storing an ontology model including classes and properties of classes, the source data schema, and the target data schema;

a schema parser for identifying a first primary data construct within the source data schema, for identifying a secondary data construct within the first primary data construct, for identifying a second primary data construct within a target data schema, and for identifying a second secondary data construct within the second primary data construct;

a schema mapper for mapping the first primary data construct to a corresponding class of the ontology model, for mapping the first secondary data construct to a property of the corresponding class of the ontology model, for mapping the second primary data construct to a corresponding class of the ontology model, and for mapping the second secondary data construct to a property of the corresponding class of the ontology model; and

a transformation generator for deriving the transformation from the first data into the second data, wherein the transformation is based on mappings mapped by the schema mapper.

26. The system of claim 25 wherein the ontology model includes a generic industry model.

27. The system of claim 25 wherein the ontology model includes an enterprise specific model.

28. The system of claim 25 wherein the ontology model includes business rules that relate properties of a class.

29. The system of claim 28 wherein the business rules include conversion rules, for converting among properties of a class.

30. The system of claim 25 wherein the ontology model is a distributed model.

31. The system of claim 25 further comprising a meta-model user interface for marking primary and secondary data constructs described within the meta-model that are to be mapped to corresponding classes and properties.

32. The system of claim 25 wherein said schema mapper manually maps the first primary data construct and the first secondary data construct.

33. The system of claim 25 wherein said schema mapper automatically maps the first primary data construct and the first secondary data construct, based on matching at least partial names between the first primary data construct and the second primary data construct, and between the first secondary data construct and the second secondary data construct, respectively.

34. The system of claim 25 wherein said schema mapper automatically maps the first secondary data construct, based on matching data types between the first secondary data construct and a property of the corresponding class.

35. The system of claim 25 wherein said schema mapper generates a Resource Description Framework (RDF) expression.

36. The system of claim 25 wherein said schema mapper maps a function of the first secondary data construct to the property of the corresponding class of the ontology model.

37. The system of claim 25 wherein said schema parser is accessed through an application programming interface (API).

38. The system of claim 25 wherein said schema parser is accessed through a graphical user interface (GUI).

39. The system of claim 25 further comprising a statistical processor calculating statistics for the ontology model.

40. The system of claim 25 further comprising a statistical processor calculating statistics for the source data schema.

41. The system of claim 40 wherein the statistics for the source data schema include a number of primary data constructs within the first data schema that have been mapped to corresponding classes of the ontology model.

42. The system of claim 40 wherein the statistics for the source data schema include a number of secondary data constructs within the source data schema that have been mapped to corresponding properties of the ontology model.

43. The system of claim 40 wherein the statistics for the source data schema include a percentage of primary data constructs within the source data schema that have been mapped to corresponding classes of the ontology model.

44. The system of claim 40 wherein the statistics for the source data schema include a percentage of secondary data constructs within the source data schema that have been mapped to corresponding properties of the ontology model.

45. A system for generating a transformation for transforming first data conforming with a source data schema to second data conforming to a target data schema, the system comprising:

a memory for storing an ontology model including classes and properties of classes, each property having associated therewith a target class, the source data schema, and the target data schema;

a schema mapper for mapping the first primary data construct to a corresponding class of the ontology model, for mapping the first secondary data construct to an inverse of a property whose target class is the corresponding class of the ontology model, for mapping the second primary data construct to a corresponding class of the ontology model, and for mapping the second secondary data construct to an inverse of a property whose target class is the corresponding class of the ontology model; and

a transformation generator for deriving the transformation from the first data into the second data, wherein the transformation is based on the mappings mapped by the schema mapper.

46. A system for generating a transformation for transforming first data conforming with a first data schema to second data conforming to a second data schema, the system comprising:

a memory for storing an ontology model including classes and properties of classes, and including inheritance relationships for superclasses, the source data schema, and the target data schema;

a schema mapper for mapping the first primary data construct to a corresponding class of the ontology model, for mapping the first secondary data construct to a property of a superclass of the corresponding class of the ontology model, for mapping the second primary data construct to a corresponding class of the ontology model, and for mapping the second secondary data construct to a property of a superclass of the corresponding class of the ontology model; and

a transformation generator for deriving the transformation from the first data into the second data, wherein the transformation is based on the mappings mapped by the schema mapper.

47. A system for generating a transformation for transforming first data conforming with a first data schema to second data conforming to a second data schema, the system comprising:

a memory for storing an ontology model including classes and properties of classes, and including inheritance relationships for superclasses, the source data schema, and the target data schema, wherein the target data schema is different from the source data schema;

a schema parser for identifying a first primary data construct within source data schema, for identifying a secondary data construct within the first primary data construct, for identifying a second primary data construct within a target data schema, and for identifying a second secondary data construct within the second primary data construct;

a schema mapper for mapping the first primary data construct to a corresponding class of the ontology model, for mapping the first secondary data construct to an inverse of a property whose target class is a superclass of the corresponding class of the ontology model, for mapping the second primary data construct to a corresponding class of the ontology model, and for mapping the second secondary data construct to an inverse of a property whose target class is a superclass of the corresponding class of the ontology model; and

a transformation generator for deriving the transformation from the first data into the second data, wherein the transformation is based on the mappings mapped by the schema mapper.

48. A system for generating a transformation for transforming first data conforming with a first data schema to second data conforming to a second data schema, the system comprising:

a memory for storing an ontology model including classes and properties of classes, the source data schema, and the target data schema, wherein the target data schema is different from the source data schema;

a schema mapper for mapping the first primary data construct to a corresponding class of the ontology model, for mapping the first secondary data construct to a composition of properties, one of which is a property of the corresponding class of the ontology model, for mapping the second primary data construct to a corresponding class of the ontology model, and for mapping the second secondary data construct to a composition of properties, one of which is a property of the corresponding class of the ontology model; and

a transformation generator for deriving the transformation from the first data into the second data, wherein the transformation is based on the mappings mapped by the schema mapper.

49. A method executed in a computer for deriving a transformation for transforming first metadata conforming with a source data schema to second metadata conforming to a target data schema, comprising:

providing a metamodel for metadata including atomic constructs and composite constructs;

providing the source schema for metadata;

providing the target schema for metadata, wherein the target schema is different from the source schema;

identifying a first primary and a first secondary metadata construct within the source schema for metadata;

identifying a second primary and a second secondary metadata construct within the target schema for metadata

generating a first mapping for mapping the first primary and the first secondary metadata constructs to corresponding composite and atomic constructs of the metamodel, respectively;

generating a second mapping for mapping the second primary and the second secondary metadata constructs to corresponding composite and atomic constructs of the metamodel, respectively; and

deriving the transformation from the first metadata into the second metadata, wherein the transformation is based on the first mapping and the second mapping.

50. The method of claim 49 wherein the source data schema is an XML Metadata Interchange (XMI) schema.

51. The method of claim 49 wherein the metamodel is a Meta-Object Facility (MOF) model.

52. A method executed in a computer for mapping a business data schema into a generic data schema, the method comprising:

providing the business data schema, wherein the business data schema represents at least one type of business data instance in terms of alphanumeric values and links to business data instances;

providing a plurality of generic instance mappings;

defining a mapping from the business data schema into the generic data schema;

representing the mapping from the business data schema into the generic data schema in terms of the generic instance mappings; and

deriving a transformation from first data conforming with the business data schema into second data conforming with the generic data schema, wherein the transformation is based on the generic instance mappings.

53. The method of claim 52 wherein the generic data schema is a Web Ontology Language (OWL) model.

54. The method of claim 52 wherein the business data schema is a relational database schema, wherein the at least one type of business data instance corresponds to at least one relational database table, and wherein the links to business data instances correspond to foreign keys.

55. The method of claim 52 wherein the business data schema is an XML schema, wherein the at least one type of business data instance corresponds to at least one complex type, and wherein the links to business data instances correspond to ID references.

56. The method of claim 52 wherein the business data schema is a Cobol copy book, wherein the at least one type of business data instance corresponds to at least one variable, and wherein the links to business data instances correspond to group items.

57. The method of claim 52 wherein the business data schema is an entity-relationship data model, wherein the at least one type of business data instance corresponds to at least one entity set, and wherein the links to business data instances correspond to relationships.

58. The method of claim 52 wherein the business data schema is an ontology model, wherein the at least one type of business data instance corresponds to at least one class, and wherein the links to business data instances correspond to properties.

59. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for combining two linked data instances into a single data instance.

60. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for combining two unlinked data instances into a single data instance.

61. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for separating a single data instance into two linked data instances.

62. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for separating a single data instance into two unlinked data instances.

63. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for linking two unlinked data instances.

64. The method of claim 52 wherein the plurality of generic instance mappings include a mapping for unlinking two linked data instances.

65. The method of claim 52 further comprising deriving a transformation from the business data schema into a second business data schema, using results of said representing.

66. The method of claim 52 further comprising transforming instances of the business data schema into corresponding instances of a second business data schema, using results of said representing.

67. The method of claim 52 further comprising deriving a query on the business data schema corresponding to a query on the generic data schema, using results of said representing.

68. A system for mapping a business data schema into a generic data schema, the system comprising:

a memory for storing the business data schema, wherein the business data schema represents at least one type of business data instance in terms of alphanumeric values and links to business data instances, and including a plurality of generic instance mappings;

a mapping generator for defining a mapping from the business data schema into the generic data schema

a mapping analyzer for representing the mapping from the business data schema into the generic data schema in terms of the generic instance mappings; and

a transformation generator for deriving a transformation from first data conforming with the business data schema into second data conforming with the generic data schema, wherein the transformation is based on the generic instance mappings.

69. The system of claim 68 wherein the generic data schema is a Web Ontology Language (OWL) model.

70. The system of claim 68 wherein the business data schema is a relational database schema, wherein the at least one type of business data instance corresponds to at least one relational database table, and wherein the links to business data instances correspond to foreign keys.

71. The system of claim 68 wherein the business data schema is an XML schema, wherein the at least one type of business data instance corresponds to at least one complex type, and wherein the links to business data instances correspond to ID references.

72. The system of claim 68 wherein the business data schema is a Cobol copy book, wherein the at least one type of business data instance corresponds to at least one variable, and wherein the links to business data instances correspond to group items.

73. The system of claim 68 wherein the business data schema is an entity-relationship data model, wherein the at least one type of business data instance corresponds to at least one entity set, and wherein the links to business data instances correspond to relationships.

74. The system of claim 68 wherein the business data schema is an ontology model, wherein the at least one type of business data instance corresponds to at least one class, and wherein the links to business data instances correspond to properties.

75. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for combining two linked data instances into a single data instance.

76. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for combining two unlinked data instances into a single data instance.

77. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for separating a single data instance into two linked data instances.

78. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for separating a single data instance into two unlinked data instances.

79. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for linking two unlinked data instances.

80. The system of claim 68 wherein the plurality of generic instance mappings include a mapping for unlinking two linked data instances.

81. The system of claim 68 further comprising a transformation generator for deriving a transformation from the business data schema into a second business data schema, using results of said mapping analyzer.

82. The system of claim 68 further comprising a transformation processor for transforming instances of the business data schema into corresponding instances of a second business data schema, using results of said mapping analyzer.

83. The system of claim 68 further comprising a query generator for deriving a query on the business data schema corresponding to a query on the generic data schema, using results of said representing.

84. A computer-readable storage medium storing program code for causing a computer to perform the steps of:

providing an ontology model including classes and properties of classes;

providing a source data schema;

providing a target data schema, wherein the target data schema is different from the source data schema;