Data store for software application documents

• US 7,668,873 B2
• Filed: 02/25/2005
• Issued: 02/23/2010
• Est. Priority Date: 02/25/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Little, Robert A., Jones, Brian M., Davis, Tristan A., Taleghani, Ali, Sawicki, Marcin
• Primary Examiner(s): Alam; Hosain T
• Assistant Examiner(s): LIN, SHEW FEN
• Application Number:
  US11/066,117
• Publication Number:
  US 20060195777A1
• Time in Patent Office: 1,824 Days
• Field of Search: 707/6
• US Class Current: 707/802
• CPC Class Codes: G06F 16/30 of unstructured textual data document management systems G06F16/93
• CPC Class Codes: G06F 16/80 of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML content-based retrieval of web data G06F16/95
• CPC Class Codes: G06F 40/123 Storage facilities
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting

Abstract

A data store is provided for storing, relating and for allowing use of data associated with a computer-generated document. Data for structuring information associated with a document, such as document metadata, is maintained in the data store where relationships between different pieces of data are maintained in a location distinct from the surface level view of a document. The data store exposes interfaces to the various pieces of data in the data store for allowing different applications to access and operate on one or more of the data pieces. The pieces of data may be structured according to a markup language such as the Extensible Markup Language (XML), and XML schemas may be associated with each piece of data for allowing the data store to validate the structure applied to the data based on an XML schema associated with a given piece of data.

Claims

1. A computer-implemented method for generating an accessible metadata store in a source document, the method comprising:

generating a source document on a source application, wherein the source document includes surface view data that is exposed on a presentation layer when the source document is rendered and metadata that is unexposed on the presentation layer when the source document is rendered;

structuring the metadata of the source document into a mark-up language (ML) document;

storing the ML document that includes the metadata of the source document in the metadata store separate from the surface view data of the source document, wherein the metadata store and the surface view data are stored in the source document;

attaching an ML schema file to the ML document that includes the metadata of the source document, wherein the ML schema file is stored in the metadata store of the source document;

exposing application programming interfaces (APIs) to the metadata store, wherein the APIs provide other applications having application types different than the source application access to the ML document that includes the metadata of the source document via object models of the other applications, wherein the exposed APIs for the metadata store permit the other applications to;

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store, receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.

2. The computer-implemented method of claim 1, wherein the ML document is an Extensible Mark-up Language (XML) document.

3. The computer-implemented method of claim 1, wherein structuring the metadata of the source document into a ML document includes structuring the metadata into a plurality of ML documents, wherein each of the plurality of ML documents includes a portion of the metadata of the source document.

4. The computer-implemented method of claim 1, wherein the ML document is validated by the ML schema file.

5. The computer-implemented method of claim 1, wherein the surface view data is stored in the source document in a separate data store from the metadata store.

6. The computer-implemented method of claim 1, wherein the exposed APIs permit other applications to simultaneously:

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.

7. A computer-readable storage medium having computer executable instructions for generating an accessible metadata store in a source document, the instructions comprising:

generating a source document on a source application, wherein the source document includes surface view data that is exposed on a presentation layer when the source document is rendered and metadata that is unexposed on the presentation layer when the source document is rendered;

structuring the metadata of the source document into a mark-up language (ML) document;

storing the ML document that includes the metadata of the source document in the metadata store separate from the surface view data of the source document, wherein the metadata store and the surface view data are stored in the source document;

attaching an ML schema file to the ML document that includes the metadata of the source document, wherein the ML schema file is stored in the metadata store of the source document;

exposing application programming interfaces (APIs) to the metadata store, wherein the APIs provide other applications having application types different than the source application access to the ML document that includes the metadata of the source document via object models of the other applications, wherein the exposed APIs for the metadata store permit the other applications to;

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store, receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.

8. The computer-readable storage medium of claim 7, wherein the ML document is an Extensible Mark-up Language (XML) document.

9. The computer-readable storage medium of claim 7, wherein structuring the metadata of the source document into a ML document includes structuring the metadata into a plurality of ML documents, wherein each of the plurality of ML documents includes a portion of the metadata of the source document.

10. The computer-readable storage medium of claim 7, wherein the ML document is validated by the ML schema file.

11. The computer-readable storage medium of claim 7, wherein the surface view data is stored in the source document in a separate data store from the metadata store.

12. The computer-readable storage medium of claim 7, wherein the exposed APIs permit other applications to simultaneously:

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store, receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.

13. A system for generating an accessible metadata store in a source document, the system comprising:

a processor; and

a memory having computer-executable instructions stored thereon, wherein the computer executable instructions are configured for;

generating a source document on a source application, wherein the source document includes surface view data that is exposed on a presentation layer when the source document is rendered and metadata that is unexposed on the presentation layer when the source document is rendered;

structuring the metadata of the source document into a mark-up language (ML) document;

storing the ML document that includes the metadata of the source document in the metadata store separate from the surface view data of the source document, wherein the metadata store and the surface view data are stored in the source document;

attaching an ML schema file to the ML document that includes the metadata of the source document, wherein the ML schema file is stored in the metadata store of the source document;

exposing application programming interfaces (APIs) to the metadata store, wherein the APIs provide other applications having application types different than the source application access to the ML document that includes the metadata of the source document via object models of the other applications, wherein the exposed APIs for the metadata store permit the other applications to;

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store, receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.

14. The system of claim 13, wherein the ML document is an Extensible Mark-up Language (XML) document.

15. The system of claim 13, wherein structuring the metadata of the source document into a ML document includes structuring the metadata into a plurality of ML documents, wherein each of the plurality of ML documents includes a portion of the metadata of the source document.

16. The system of claim 13, wherein the ML document is validated by the ML schema file.

17. The system of claim 13, wherein the surface view data is stored in the source document in a separate data store from the metadata store.

18. The system of claim 13, wherein the exposed APIs permit other applications to simultaneously:

load the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

monitor modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

modify the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data,

when a modification of the metadata is received at the metadata store, receive a change notification from the metadata store of a modification to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data, and

undo modifications to the metadata, stored in the metadata store that is stored in the source document, independent of the surface view data.