System and method for synchronizing and/or updating an existing relational database with supplemental XML data

• US 7,031,956 B1
• Filed: 10/09/2001
• Issued: 04/18/2006
• Est. Priority Date: 02/16/2000
• Status: Active Grant

• Current Assignee: Masonic Holdings Limited Liability Company
• Original Assignee: Verizon Laboratories Incorporated (Verizon Communications Inc.)
• Inventors: Rundensteiner, Elke Angelika, Zhang, Xin, Mitchell, Gail Anne, Lee, Wang-Chien
• Primary Examiner(s): Corrielus, Jean
• Assistant Examiner(s): Ly, Anh
• Application Number:
  US09/973,514
• Time in Patent Office: 1,652 Days
• Field of Search: 707 1- 10, 707100-204
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A system and a method for synchronizing and updating a relational database with supplemental data in which the relational database has a set of tables defined by a relational schema. The supplemental data preferably comprises data in a tagged format having a document-type definition representative of the relational schema and is represented in a document object. The system and method preferably ensure record-by-record updating and synchronization of the relational database with the at least one proposed data update by receiving at least one proposed data update from a source external to the relational database; and propagating the received at least one proposed data update into the relational database. In this matter, the compliance with both the relational database relational schema and the tagged data document type definition is ensured without requiring reloading existing data in the relational database.

Claims

1. A method for synchronizing and updating a relational database containing existing data with supplemental data, the relational database having a set of tables defined by a relational schema, the supplemental data comprising formatted data having a document type definition representative of the relational schema, the method comprising the steps of:

receiving at least one proposed data update representative of the supplemental data from a source external to the relational database, the supplemental data being represented by a document object; and

propagating the received at least one proposed data update into the relational database in a manner which ensures compliance with both the relational database relational schema and the document type definition without requiring reloading the existing data in the relational database, said propagating step comprising the sub-steps of

traversing the document object to determine at least one path expression identifying at least one element of the document object, said at least one element being identified by said at least one proposed data update, and

using said at least one path expression to determine relational identifiers of data to be updated in the relational database.

2. The method of claim 1 wherein said formatted data is tagged-format data.

3. The method of claim 2 further comprising the step of providing at least one update primitive for accomplishing the step of propagating the received at least one proposed data update.

4. The method of claim 3 further comprising the step of selectively calling the at least one update primitive and validating an output of the at least one update primitive against the document type definition.

5. The method of claim 4 wherein the at least one update primitive further comprises at least one of a create root element primitive, a modify element primitive, a delete leaf element primitive and a move element primitive.

6. The method of claim 5 wherein the create root element primitive creates a new unattached root element in the document object representative of the at least one proposed data update.

7. The method of claim 6 wherein the modify element primitive modifies a specified attribute of an identified element of the document object representative of the at least one proposed data update.

8. The method of claim 7 wherein the delete leaf element primitive removes an identified element of the document object representative of the at least one proposed data update.

9. The method of claim 8 wherein the move element primitive changes the document object location of an identified element of the document object representative of the at least one proposed data update.

10. The method of claim 9 further comprising the step of calling both the create element primitive and the move element primitive to create a new element in the document object and to attach the newly-created element within the document object at a desired location within the document object when the at least one proposed data update calls for the creation of a new element.

11. The method of claim 1 wherein said path expression is formed in an XPath syntax.

12. The method of claim 1 further comprising the step of converting an object identifier of said at least one element into said at least one path expression.

13. The method of claim 1 wherein said traversing step is performed in a child-to-parent direction to build said at least one path expression.

14. The method of claim 13 wherein said path expression comprises at least one node indicator comprising label value and a position value corresponding to the document object.

15. The method of claim 14 wherein successive node indicators are separated by a preselected delimiter.

16. The method of claim 14 wherein the position value corresponds to a lateral sibling location in the document object.

17. The method of claim 14 wherein the label value is selected based upon a node type of a predetermined node.

18. The method of claim 1 further comprising the step of validating the at least one proposed data update to ensure the at least one proposed data update is compliant with the document type definition.

19. The method of claim 18 further comprising the step of determining whether at least one of a type constraint and an attribute constraint remain valid when at least one of a new value of a document object attribute value is set and a new document object is created.

20. The method of claim 19 further comprising the step of determining whether a cross-reference index is unique within the document object during the step of validating the at least one proposed data update.

21. The method of claim 20 further comprising the step of determining whether a default value is required during the creation of a new element in accordance with the at least one proposed data update during the step of validating the at least one proposed data update.

22. The method of claim 21 further comprising the step of determining whether an enumerated value is required by the at least one proposed data update and determining whether a proposed value therefore is contained in a specified enumeration during the step of validating the at least one proposed data update.

23. The method of claim 22 further comprising the step of checking a nesting relationship between a former and a new location of an element when an element is moved in accordance with the at least one proposed data update during the step of validating the at least one proposed data update.

24. The method of claim 23 further comprising the step of determining a quantitative relationship between the at least one proposed data update and the relational database and determining whether the at least one proposed data update complies with such quantitative relationship as determined by the document type definition.

25. The method of claim 23 further comprising the step of checking a quantifier constraint of a nesting relationship between elements implicated by the at least one proposed data update and determining whether the at least one proposed data update violates that quantifier constraint.

26. The method of claim 25 further comprising the step of preventing the propagation step from occurring if the at least one proposed data update fails the validation step.

27. The method of claim 1 wherein said propagating step further comprises:

translating said proposed data update into a set of update primitives;

executing said set of update primitives to transform said at least one element of the document object in accordance with said proposed data update;

mapping said set of update primitives to relational operations; and

applying said relational operations to said data identified by said relational identifiers.

28. A method for both generating a relational schema for a relational database corresponding to a document having a document-type definition and data complying with the document-type definition, the document-type definition having content particles representative of the structure of the data and loading the data into the relational database in a manner consistent with the relational schema, the method comprising the steps of:

extracting metadata representative of the document-type definition from the document-type definition;

generating the relational schema from the metadata, thereby defining via the metadata at least one table in the relational database corresponding to at least one of the content particles of the document-type definition;

loading the data into the at least one table according to the relational schema and in a manner driven by the metadata; and

updating the relational database with at least one proposed update associated with supplemental data represented by a document object, said updating step comprising the sub-steps of

traversing the document object to determine at least one path expression identifying at least one element of the document object, said at least one element being identified by said at least one proposed data update,

using said at least one path expression to determine relational identifiers of at least a subset of the data in the relational database, and

applying at least one relational operation to said at least a subset of the data in the relational database to update said at least a subset of the data in accordance with said at least one proposed update.

29. The method of claim 28 further comprising the step of loading data from the document into the relational schema of the relational database.

30. The method of claim 28 further comprising the step of validating the at least one proposed update with respect to the document-type definition.

31. The method of claim 30 further comprising the step of preventing the at least one proposed update from being loaded into the relational database if the validating step fails.

32. The method of claim 30 wherein the step of validating the at least one proposed update further comprises the step of comparing at least one of a data type constraint, an attribute constraint, a link reference constraint, a nesting relationship constraint and a quantifier constraint of the at least one proposed update against that required by the document-type definition prior to the step of loading the data from the at least one proposed update into the relational database.

33. A system for synchronizing and updating a relational database containing existing data with supplemental data, the relational database having a set of tables defined by a relational schema, the supplemental data comprising formatted data having a document type definition representative of the relational schema, comprising:

a translator for receiving at least one proposed data update representative of the supplemental data from a source external to the relational database, the supplemental data being represented by a document object; and

an execution device operably connected to the translator for propagating the received at least one proposed data update into the relational database in a manner which ensures compliance with both the relational database relational schema and the document type definition without requiring reloading the existing data in the relational database, said execution device being configured to perform the steps of;

traversing the document object to determine at least one path expression identifying at least one element of the document object, said at least one element being identified by said at least one proposed data update; and

using said at least one path expression to determine relational identifiers of data to be updated in the relational database.

34. The system of claim 33 wherein said formatted data is tagged-format data.

35. The system of claim 33 further comprising at least one update primitive for propagating the received at least one proposed data update to the execution device.

36. The system of claim 33 wherein the at least one update primitive is selectively called in order to validate an output of the at least one update primitive against the document type definition.

37. The system of claim 36 wherein the at least one update primitive further comprises at least one of a create root element primitive, a modify element primitive, a delete leaf element primitive and a move element primitive.

38. The system of claim 37 wherein the create root element primitive creates a new unattached root element in the document object representative of the at least one proposed data update.

39. The system of claim 38 wherein the modify element primitive modifies a specified attribute of an identified element of the document object representative of the at least one proposed data update.

40. The system of claim 39 wherein the delete leaf element primitive removes an identified element of the document object representative of the at least one proposed data update.

41. The system of claim 40 wherein the move element primitive changes the document object location of an identified element of the document object representative of the at least one proposed data update.

42. The system of claim 41 wherein the create element primitive and the move element primitive create a new element in the document object and attach the newly-created element within the document object at a desired location within the document object when the at least one proposed data update calls for the creation of a new element.

43. The system of claim 36 wherein the at least one update primitive further comprises a create root element primitive, a modify element primitive, a delete leaf element primitive, and a move element primitive.

44. The system of claim 43 wherein the create root element primitive, the modify element primitive, the delete leaf element primitive, and the move element primitive form a complete set of operations for transforming any first document object tree into any second document object tree, wherein the first document object tree and the second document object tree each comply with the same document type definition.

45. The system of claim 33 wherein said path expression is formed in an XPath syntax.

46. The system of claim 33 wherein the translator converts an object identifier of said at least one element into said at least one path expression during the translation of said at least one proposed data update.

47. The system of claim 33 wherein the translator traverses the document object in a child-to-parent direction to build said at least one path expression.

48. The system of claim 47 wherein said path expression comprises at least one node indicator comprising label value and a position value corresponding to the document object.

49. The system of claim 48 wherein successive node indicators are separated by a preselected delimiter.

50. The system of claim 48 wherein the position value corresponds to a lateral sibling location in the document object.

51. The system of claim 48 wherein the label value is selected based upon a node type of a predetermined node.

52. The system of claim 33 further comprising a validator which determines whether the at least one proposed data update is compliant with the document-type definition.

53. The system of claim 52 wherein the validator determines whether at least one of a type constraint and an attribute constraint remain valid when at least one of a new value of a document object attribute value is set and a new document object is created.

54. The system of claim 53 wherein the validator determines whether a cross-reference index is unique within the document object.

55. The system of claim 54 wherein the validator determines whether a default value is required during the creation of a new element in accordance with the at least one proposed data update.

56. The system of claim 55 wherein the validator determines whether an enumerated value is required by the at least one proposed data update and determines whether a proposed value therefore is contained in a specified enumeration.

57. The system of claim 56 wherein the validator checks a nesting relationship between a former and a new location of an element when an element is moved in accordance with the at least one proposed data update.

58. The system of claim 57 wherein the validator checks a quantifier constraint of a nesting relationship between elements implicated by the at least one proposed data update and determines whether the at least one proposed data update violates that quantifier constraint.

59. The system of claim 58 wherein the execution device prevents the at least one proposed data update from propagating to the relational database upon a validation failure signal from the validator.

60. The system of claim 57 wherein the validator determines a quantitative relationship between the at least one proposed data update and the relational database and determines whether the at least one proposed data update complies with such quantitative relationship as determined by the document type definition.

61. A system for both generating a relational schema for a relational database corresponding to a document having a document-type definition and data complying with the document-type definition, the document-type definition having content particles representative of the structure of the data and loading the data into the relational database in a manner consistent with the relational schema, comprising:

an extractor for creating metadata representative of the document-type definition from the document-type definition;

a generator for forming the relational schema from the metadata, thereby defining via the metadata at least one table in the relational database corresponding to at least one of the content particles of the document-type definition;

a loader for loading the data into the at least one table according to the relational schema and in a manner driven by the metadata; and

a synchronizer for updating the relational database with at least one proposed update from a second document containing related data without requiring the reloading of the data already in the relational database by the loader, said synchronizer being configured to;

traverse the second document to determine at least one path expression identifying at least one element of the second document, said at least one element being identified by said at least one proposed data update;

use said at least one path expression to determine relational identifiers of at least a subset of the data in the relational database; and

apply at least one relational operation to said at least a subset of the data in the relational database to update said at least a subset of the data in accordance with said at least one proposed update.

62. The system of claim 61 further comprising a validator for validating the at least one proposed update with respect to the document-type definition.

63. The system of claim 62 wherein the validator prevents the at least one proposed update from being loaded into the relational database by the synchronizer by sending a signal to the synchronizer.

64. The system of claim 63 wherein the validator compares at least one of a data type constraint, an attribute constraint, a link reference constraint, a nesting relationship constraint and a quantifier constraint of the at least one proposed update against that required by the document type definition prior to signaling the synchronizer to load the at least one proposed update into the relational database.

65. A method of synchronizing and updating existing data of a relational database, the method comprising:

receiving a proposed data update from a source external to the relational database, said proposed data update being represented by a document object;

translating said proposed data update into a set of update primitives;

executing said set of update primitives to transform at least one element of the document object in accordance with said proposed data update;

traversing the document object to determine a path expression identifying said at least one element of the document object;

using said path expression to determine relational identifiers identifying data in the relational database; and

propagating said proposed data update into the relational database by mapping said set of update primitives to relational operations and applying said relational operations to said data identified by said relational identifiers.

66. The method of claim 65 further comprising validating said proposed data update by comparing said proposed data update with a plurality of relational tables containing relational schema representative of document type definition metadata.

67. The method of claim 66 wherein said plurality of relational tables includes a first table, a second table, and a third table, said first table comprising item metadata, said second table comprising attribute metadata, and said third table including nested relationship metadata.

68. The method of claim 65 wherein said relational identifiers comprise a table identifier and a tuple identifier, and said relational operations comprise said path expression having said relational identifiers as inputs.