System and method for XML based content management

• US 6,910,040 B2
• Filed: 04/12/2002
• Issued: 06/21/2005
• Est. Priority Date: 04/12/2002
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Barta, Michael L., Emmick, David J., Waibel, Bryn Christopher
• Primary Examiner(s): Rones, Charles
• Assistant Examiner(s): ABEL JALIL, NEVEEN
• Application Number:
  US10/121,767
• Publication Number:
  US 20030195885A1
• Time in Patent Office: 1,166 Days
• Field of Search: 707 1- 10, 707100-1041, 707/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

System and method for a content management system are described. The content management system takes complex hierarchically represented content structures and represents the hierarchical model by way of a relational model that creates node tables and edge tables to represent various content structures. Moreover, the content is separated from the structure such that the same content units may be used by multiple content structures.

Claims

1. A computer readable medium bearing computer readable instructions for carrying out the process of

parsing information arranged in a hierarchical order into a plurality of content units arranged in a hierarchical structure comprising at least one parent node, at least one leaf node, and at least one edge relating the parent node and the leaf node wherein the leaf node is indicative of at least one of the plurality of content units, the parent node and the edge are indicative of a hierarchical order of the information;

providing a relational database comprising a node table and an edge table; and

storing the hierarchical structure in the relational database such that the information indicative of the edge is stored in the edge table, information indicative of the parent node is stored within the node table, and information indicative of the leaf node is stored in the node table; and

content units are stored in a location accessible by the database whereby the location of the content unit can be determined from the information indicative of the leaf node.

2. A content management system, comprising:

computer readable instructions that parse information arranged in a hierarchical order into a plurality of content units arranged in a hierarchical structure comprising at least one parent node, at least one leaf node, and at least one edge relating the parent node and the leaf node wherein the leaf node is indicative of at least one of the plurality of content units, the parent node and the edge are indicative of a hierarchical order of the information;

a relational database comprising a node table and an edge table;

computer readable instructions that store the hierarchical structure in the relational database such that the information indicative of the edge is stored in the edge table, information indicative of the parent node is stored within the node table, and information indicative of the leaf node is stored in the node table; and

content units are stored in a location accessible by the database whereby the location of the content unit can be determined from the information indicative of the leaf node.

3. The system as recited in claim 2 wherein the at least one parent node is indicative of a category of the content unit.

4. The system as recited in claim 2 wherein the content unit comprises text.

5. The system as recited in claim 2 wherein the content unit comprises a graphic.

6. The system as recited in claim 2 further comprising an ownership structure, wherein the ownership structure associated with a content unit is stored in a relational table.

7. The system as recited in claim 2 wherein the content unit is stored in a file pointed to by the information indicative of the leaf node.

8. The system as recited in claim 2 wherein the content unit is stored in the relational database.

9. The system as recited in claim 2 comprising a second leaf node wherein the leaf node and the second leaf node each have an edge to the parent node.

10. The system as recited in claim 2 wherein the node table further comprises information indicative of a second leaf node associated with a second hierarchical order and wherein the second leaf and the leaf node are associated with the same content unit.

11. A method for storing information in an a content management system, comprising:

parsing information arranged in a hierarchical order into a plurality of content units arranged in a hierarchical structure comprising at least one parent node, at least one leaf node, and at least one edge relating the parent node and the leaf node wherein the leaf node is indicative of at least one of the plurality of content units, the parent node and the edge are indicative of a hierarchical order of the information;

providing a relational database comprising a node table and an edge table;

storing the hierarchical structure in the relational database such that the information indicative of the edge is stored in the edge table, information indicative of the parent node is stored within the node table, and information indicative of the leaf node is stored in the node table; and

content units are stored in a location accessible by the database whereby the location of the content unit can be determined from the information indicative of the leaf node.

12. The method as recited in claim 11 wherein the at least one parent node is indicative of a category of the content unit.

13. The method as recited in claim 11 wherein the content unit comprises text.

14. The method as recited in claim 11 wherein the content unit comprises a graphic.

15. The method as recited in claim 11 further comprising an ownership structure, wherein the ownership structure associated with a content unit is stored in a relational table.

16. The method as recited in claim 11 wherein the content unit is stored in a file pointed to by the information indicative of the leaf node.

17. The method as recited in claim 11 wherein the content unit is stored in the relational database.

18. The method as recited in claim 11 comprising a second leaf node wherein the leaf node and the second leaf node each have an edge to the parent node.

19. The method as recited in claim 11 wherein the node table further comprises information indicative of a second leaf node associated with a second hierarchical order and wherein the second leaf and the leaf node are associated with the same content unit.

20. The method as recited in claim 11 wherein the hierarchical order comprises an ordering based on internal document divisions.

21. The method as recited in claim 20 wherein the internal document divisions comprise chapter headings.

22. The method as recited in claim 20 wherein the internal document divisions comprise paragraph level divisions.