Systems and methods for data modeling in an item-based storage platform

• US 7,428,546 B2
• Filed: 08/21/2003
• Issued: 09/23/2008
• Est. Priority Date: 08/21/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Terek, F. Soner, Thompson, J. Patrick, Nori, Anil K., Campbell, David G., Celis, Pedro, Agarwal, Sameet
• Primary Examiner(s): Corrielus; Jean M
• Application Number:
  US10/646,580
• Publication Number:
  US 20050049993A1
• Time in Patent Office: 1,860 Days
• Field of Search: 707/101, 707/104.1, 707/103.R, 707/5, 707/10, 707/102
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• 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/99944 Object-oriented database structure

Abstract

Various embodiments of the present invention are directed to a data store comprising Items, Elements, and Relationships. An Item is a unit of data storable in a data store and further comprises said Element and said Relationship. An Element is an instance of a type comprising one or more fields. A Relationship is a link between at least two Items. The data store further comprising a Core Schema to define a set of Core Items by which a hardware/software interface system understands and directly processes said set of Core Items in a predetermined and predictable way. The Core Items are derived (directly or indirectly) from a common single Base Item which, in turn, is a foundational Item in a Base Schema.

Claims

1. A method for management of a data store comprising:

organizing the data store such that the data store comprises;

an Item;

an Element;

a plurality of Relationships comprising containment Relationships and reference Relationships, wherein the containment Relationships control the life-time of the Item, wherein said containment relationships are classified either as a holding Relationship or an embedding Relationship, wherein the Item is deleted when the holding relationship is deleted, wherein said Item is a unit of data storable in a data store and has at least one of a type or subtype, and includes said Element and said plurality of Relationships, wherein said Element is an instance of a type comprising one or more fields; and

wherein said plurality of Relationships is are a link between at least two Items;

a Base Schema that establishes a framework for creating and organizing each Item and setting the a foundational set of properties; and

a Core Schema defines a set of core types, wherein each Item is characterized into at least one core type based on the Item type or the Item subtype.

2. The method of claim 1 further comprising organizing the data store such that the data store comprises a plurality of Items, said plurality of Items comprising an Item Folder and at least one other Item that is a member of said Item Folder.

3. The method of claim 1 further comprising organizing the data store such that the data store comprises a plurality of Items, said plurality of Items comprising a Category and at least other one Item that is a member of said Category.

4. The method of claim 1 further comprising organizing the data store such that the data store comprises a second Element, and wherein said Relationship comprises said second Element.

5. The method of claim 1 wherein each Item from the set of Core Items is derived from a Common Single Base Item.

6. The method of claim 1 wherein said Common Single Base Item is a foundational Item in a Base Schema.

7. A computer readable storage medium having stored thereon computer executable instructions for performing steps comprising:

organizing the data store such that the data store comprises;

an Item;

an Element;

a plurality of Relationships comprising containment Relationships and reference Relationships, wherein the containment Relationships control the life-time of the Item, wherein said containment relationships are classified either as a holding Relationship or an embedding Relationship, wherein the Item is deleted when the holding relationship is deleted, wherein said Item is a unit of data storable in a data store and has at least one of a type or subtype and includes said Element and said plurality of Relationships, wherein said Element is an instance of a type comprising one or more fields; and

wherein said plurality of Relationships is are a link between at least two Items;

a Base Schema establishes a framework for creating and organizing each Item and setting a foundational set of; and

a Core Schema defines a set of core types, wherein each Item is characterized into at least one core type based on the Item type or the Item subtype.

8. The computer readable storage medium of claim 7 further comprising computer executable instructions for organizing the data store such that the data store comprises a plurality of Items, said plurality of Items comprising an Item Folder and at least one other Item that is a member of said Item Folder.

9. The computer readable storage medium of claim 7 further comprising computer executable instructions for organizing the data store such that the data store comprises a plurality of Items, said plurality of Items comprising a Category and at least other one Item that is a member of said Category.

10. The computer readable storage medium of claim 7 further comprising computer executable instructions for organizing the data store such that the data store comprises a second Element, and wherein said Relationship comprises said second Element.

11. A computer system comprising:

a processor; and

a memory comprising;

an Item;

an Element;

a plurality of Relationships comprising containment Relationships and reference Relationships, wherein the containment Relationships control the life-time of the Item, wherein said containment relationships are classified either as a holding Relationship or an embedding Relationship, wherein the Item is deleted when the holding relationship is deleted, wherein said Item is a unit of data storable in a data store and has at least one of a type or subtype and includes said Element and said plurality of Relationships, wherein said Element is an instance of a type comprising one or more fields; and

wherein said plurality of Relationships is are a link between at least two Items;

a Base Schema that establishes a framework for creating and organizing each Item and setting a foundational set of properties; and

a Core Schema that defines a set of core types, wherein each Item is characterized into at least one core type based on the Item type or the Item subtype.

12. The computer system of claim 11 wherein the memory comprises a plurality of Items, said plurality of Items comprising an Item Folder and at least one other Item that is a member of said Item Folder.

13. The computer system of claim 11 wherein the memory comprises a plurality of Items, said plurality of Items comprising a Category and at least other one Item that is a member of said Category.

14. The computer system of claim 11 wherein the memory comprises a second Element, and wherein said Relationship comprises said second Element.