Managing XML documents containing hierarchical database information

• US 7,318,063 B2
• Filed: 02/19/2004
• Issued: 01/08/2008
• Est. Priority Date: 02/19/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bath, Kamaljit S., Selim, Nora S., Brychell, Joseph J., Jervis, Robert, Vassiliev, Mikhail, Green, Hagen, Bocken, Xavier, Narendran, Arungundram, van Velzen, Danny
• Primary Examiner(s): Lee; Wilson
• Application Number:
  US10/783,702
• Publication Number:
  US 20050187973A1
• Time in Patent Office: 1,419 Days
• Field of Search: 715/513, 715/530, 715/500, 707 1- 10, 707/100, 707/101, 707/102, 707/104.1
• US Class Current: 715/234
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/956 Hierarchical
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Systems, methods, and computer program products for management of data that is stored in a hierarchical format such as, e.g., a relational database, when the data is retrieved and manipulated using a schema-driven format such as, e.g., XML are disclosed. In one implementation a copy of the XML data retrieved from the database and is generated and each logical unit in at least one of the original XML data or the copy of the XML data is annotated in a manner that uniquely identifies each logical unit. For example, each XML node may be assigned a unique numerical or string identifier. As the data is manipulated, algorithms may be implemented to use the annotations to track changes to the XML data and to ensure that the manipulated XML data complies with one or more required data formats. When the XML data is ready to be transferred back to the database(s) from which it was obtained, a series of operations are implemented to validate the data and to determine the nature of operation to be performed to restore the data to the databases.

Claims

1. A method of managing XML documents, comprising:

receiving an original XML document that includes information from a hierarchical database, the hierarchical database being distinct from the original XML document;

generating a copy of the original XML document;

annotating the original XML document with an identifier that uniquely identifies each node in the document and a corresponding node in the copy of the XML document;

accepting at least one edit operation to the original XML document;

modifying at least one annotation to the original XML document in response to the at least one edit operation;

identifying at least one change to the original XML document as a result of the at least one edit operation; and

updating the database to reflect the change to the original XML document.

2. The method of claim 1, wherein annotating the original XML document with an identifier that uniquely identifies each node in the document and a corresponding node in the copy of the XML document comprises assigning an annotated identifier to each node in the original XML document.

3. The method of claim 2, wherein the annotated identifier is characterized by an attribute that is assigned a namespace that uniquely identifies an update process.

4. The method of claim 3, wherein the attribute is characterized by a name that is randomly generated.

5. The method of claim 1, wherein:

annotating the original XML document with an identifier that uniquely identifies each node in the document and a corresponding node in the copy of the XML document comprises assigning an annotated identifier to each node in the original XML document; and

modifying at least one annotation to the original XML document in response to the at least one edit operation comprises removing the annotated identifier from one or more nodes that are copies of another node in the document.

6. The method of claim 1, wherein identifying at least one change to the original XML document as a result of the at least one edit operation comprises searching the original XML document for one or more new entries.

7. The method of claim 6, wherein updating the database to reflect the change to the original XML document comprises inserting the new entries into the database.

8. The method of claim 1, wherein updating the database to reflect the change to the original XML document comprises updating database data from the original XML document.

9. The method of claim 1, further comprising re-annotating the original XML document for further processing.

10. The method of claim 9, wherein re-annotating the original XML document comprises updating the XML document to reflect one or more changes to the database data.

11. A system for managing XML documents, comprising:

a computing device including a display, a user-input device, and a processing unit, and a memory module the memory module comprising;

a database module to retrieve data from a database, and to format and display the data in an original XML document, the database being distinct from the original XML document;

an XML processing module to generate a copy of the original XML document and to annotate at least one of the original XML document and the copy of the XML document with an identifier that uniquely identifies each node in the document;

an XML editing module to accept edits to the original XML document and to modify at least one annotation to the XML data in response to the at least one edit;

an XML conversion module to identify at least one change to the original XML document as a result of the at least one edit operation; and

to update the database to reflect the change to the original XML document.

12. The system of claim 11, wherein the XML processing module assigns an annotated identifier to each node in the original XML document.

13. The system of claim 12, wherein the annotated identifier is characterized by an attribute that is assigned a namespace that uniquely identifies an update process.

14. The system of claim 13, wherein the attribute is characterized by a name that is randomly generated.

15. The system of claim 11, wherein:

the XML processing module assigns an annotated identifier to each node in the original XML document; and

the XML editing module removes the annotated identifier from one or more nodes that are copies of another node in the document.

16. The system of claim 11, wherein the XML conversion module searches the original XML document for one or more new entries.

17. The system of claim 16, wherein the XML conversion module inserts one or more new entries in the original XML document into the database.

18. The system of claim 11, wherein the XML conversion module updates the database to reflect the changes to the data in the original XML data.

19. The system of claim 11, wherein the XML re-annotation module re-annotates the original XML document for further processing.

20. The system of claim 19, wherein the XML re-annotation module updates the XML document to reflect one or more changes to the database data.

21. One or more computer-readable media comprising computer executable instructions that, when executed on a computer, direct the computer to:

receive an original XML document that includes information from a hierarchical database, the hierarchical database being distinct from the original XML document;

generate a copy of the XML document;

annotate at least one of the original XML document and the copy of the XML document with an identifier that uniquely identifies each node in the document;

accept at least one edit operation to the original XML document;

modify at least one annotation to the XML in response to the at least one edit operation;

identify at least one change to the original XML document as a result of the at least one edit operation; and

update the database to reflect the change to the original XML document.

22. The one or more computer-readable media of claim 21, further comprising computer executable instruction that, when executed, direct the computer to assign an annotated identifier to each node in the original XML document.

23. The one or more computer-readable media of claim 22, wherein the annotated identifier is characterized by an attribute that is assigned a namespace that uniquely identifies an update process.

24. The one or more computer-readable media of claim 23, wherein the attribute is characterized by a name that is randomly generated.

25. The one or more computer-readable media of claim 21, further comprising computer executable instruction that, when executed, direct the computer to:

assign an annotated identifier to each node in the original XML document; and

remove the annotated identifier from one or more nodes that are copies of another node in the document.

26. The one or more computer-readable media of claim 21, further comprising computer executable instruction that, when executed, direct the computer to search the original XML document for one or more new entries.

27. The one or more computer-readable media of claim 26, further comprising computer executable instruction that, when executed, direct the computer to insert the new entries into the database.

28. The one or more computer-readable media of claim 21, further comprising computer executable instruction that, when executed, direct the computer to update database data from the original XML document.

29. The one or more computer-readable media of claim 21, further comprising logic instructions that, when executed on a computer, cause the computer to re-annotate the original XML document for further processing.

30. The computer-readable media of claim 29, further comprising computer executable instruction that, when executed, direct the computer to update the XML document to reflect one or more changes to the database data.

31. A method of managing markup language documents, comprising:

receiving an original markup language document that includes information from a hierarchical database, the hierarchical database being distinct from the original markup language document;

generating a copy of the original markup language document;

annotating the original markup language document or the copy of the markup language document with an identifier that uniquely identifies each node in the annotated markup language document and a corresponding node in the other markup language document;

accepting at least one edit operation to the annotated markup language document;

modifying at least one annotation to the annotated markup language document in response to the at least one edit operation;

identifying at least one change to the annotated markup language document as a result of the at least one edit operation; and

updating the database to reflect the change to the annotated markup language document.