LIVE ENTITIES INTERNET STORE SERVICE

• US 20080201234A1
• Filed: 02/16/2007
• Published: 08/21/2008
• Est. Priority Date: 02/16/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Castro, Pablo, Barnett, Alex Anthony, Mallalieu, Timothy Ian, Johnston, D. Britton
• Application Number:
  US11/675,933
• Publication Number:
  US 20080201234A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

The claimed subject matter provides for an online, Internet-class service that can correlate between an application interface utilizing a highly expressive, EDM conceptual format and a data store structured in an efficient, highly scalable storage format. Such a service can include components that map between an EDM schema and a data structure format. Additionally, a query reply can include data presented with a payload format distinct from an EDM query format.

Claims

1. A system that provides network data storage as a service, comprising:

a data store that includes a storage model that defines a structure of data storage;

a REST interface that can facilitate information exchange to and from the data store; and

a mapping component that can correlate between the data storage model and an EDM conceptual model, where the data storage model and the EDM conceptual model are different.

2. The system of claim 1, the data storage model includes an efficient storage schema.

3. The system of claim 1, the EDM conceptual model includes a rich, highly expressive EDM schema.

4. The system of claim 1, the data store is an Internet data store, the storage model is an Internet-scale database storage model.

5. The system of claim 1, the data store is an Intranet data store, the storage model is a structured query language (SQL) database storage model.

6. The system of claim 1, further comprising a client application that can interact with the data store by way of the REST interface and mapping component.

7. The system of claim 6, the client application interacts with the data store according to the EDM conceptual model by way of the REST interface.

8. The system of claim 6, the data store interacts with the client application according to the storage model by way of the REST interface.

9. A method for providing a commercially available database service platform, comprising:

converting between an EDM data structure and a highly scalable storage modeling structure;

exposing a data store modeled with the highly scalable data structure over a web-scale network by way of a REST interface; and

providing varying levels of access, or support for such access, or both, at levels of compensation that correspond at least to the levels of access, support, or both.

10. The method of claim 9, further comprising providing a consumer-ready application user-interface to access the data store, or a direct access REST-style API interface to access the data store, or both.

11. A method for providing network data storage as a service comprising:

receiving an application conceptual model expressed by way of an entity data model (EDM) characterization;

mapping a correlation between the EDM characterization and a storage characterization format; and

providing a representational state transfer (REST) interface enabling stateless, uniform interaction with data in a data store.

12. The system of claim 11, further comprising providing a web-scale network data store for storage of data related to the application conceptual model, the data store structured according to the storage characterization format.

13. The method of claim 11 further comprising transmitting data from the store in response to a query.

14. The method of claim 12, the entities are in a form useful to an application associated with the application conceptual model.

15. The method of claim 11, the EDM specifies at least one of an Entity type, Entity instance, or an Entity set, a Relationship type, Relationship instance, or Relationship set, or an Action type, Action instance, or Action set, or a combination thereof.

16. The method of claim 12, further comprising applying an EDM schema, defined by the EDM characterization, to interaction with data in the data store.

17. The method of claim 15, further comprising defining a storage schema for the data store distinct from the EDM schema applied to the interaction with data in the data store.

18. The method of claim 16, further comprising mapping a correlation between the EDM schema applied to the interaction with data in the data store and the storage schema for the data store.

19. The method of claim 16, the storage schema is an EDM schema, distinct from the EDM schema defined by the EDM characterization.

20. The method of claim 12, the data transmitted from the store is characterized by a data representation format that can include java script object notation (JSON), resource description framework (RDF), or plain old extensible mark-up language (POX), or a combination thereof.