Schema-based services for identity-based data access to document data

• US 20040199861A1
• Filed: 08/06/2002
• Published: 10/07/2004
• Est. Priority Date: 03/14/2001
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Lucovsky, Mark H.
• Application Number:
  US10/213,525
• Publication Number:
  US 20040199861A1
• Time in Patent Office: Days
• US Class Current: 715/225
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6236 between heterogeneous systems
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G06F 2221/2117 User registration
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/62 : Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: Y10S 707/99931 : Database or file accessing
• CPC Class Codes: Y10S 707/99939 : Privileged access
• 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

Abstract

A schema-based documents service for Internet access to per-user documents data, wherein access to data is based on each user'"'"'s identity. The documents service includes a schema that defines rules and a structure for each user'"'"'s data, and also includes methods that provide access to the data in a defined way. The documents schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the documents schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user'"'"'s identification, defined role and scope for that role. In this way, document data can be accessed by its owner, and shared to an extent determined by the owner. The structure of the data is defined from the perspective of the data, not from that of an application program or a device, whereby appropriate programs can communicate with the documents service to access the data, with existing knowledge of the schema-defined format, regardless of the device or application program in use. Extensibility is defined into the schema.

Claims

1. In a computer network, a method comprising,

providing a documents schema, the documents schema having document-related fields arranged into a content document with defined structures for the fields;

receiving a data access request directed to a document, the request including associated identity information; and

in response to the data access request, manipulating at least one set of data in a logical documents document that includes data therein according to the associated identity information, each set of data in the logical documents document structured to correspond to a field in the content document.

2. The method of claim 1 wherein manipulating at least one set of data comprises reading data from at least one field in the logical documents document.

3. The method of claim 1 wherein manipulating at least one set of data comprises writing data to at least one field in the logical documents document.

4. A computer-readable medium having computer-executable instructions for performing the method of claim 1.

5. In a computer network, a method comprising,

receiving a request to retrieve document data, the request including associated identity information;

reading from a data store to obtain document data based on the associated identity information;

constructing a document response including at least part of the data, the document response arranged according to a defined schema for documents data; and

returning the document response in response to the request.

6. The method of claim 5 wherein the schema includes at least one defined field for extending the schema.

7. A computer-readable medium having computer-executable instructions for performing the method of claim 5.

8. A computer-readable medium having stored thereon a data structure, comprising:

a first set of data that identifies a document;

a second set of data that provides information about the document;

a third set of data corresponding to content of the document; and

wherein the first, second and third sets of data are regularized according to a schema in a documents service such that a recipient of the data structure interprets the data according to the schema.

9. The data structure of claim 9 wherein the first set of data includes data corresponding to a document name.

10. The data structure of claim 9 wherein the first set of data includes data corresponding to a document identifier.

11. The data structure of claim 9 wherein the second set of data includes data corresponding to a document folder identifier.

12. The data structure of claim 11 wherein the second set of data includes data corresponding to attributes of a folder corresponding to the folder identifier.

13. The data structure of claim 9 wherein the second set of data includes data corresponding to attributes of the document.

14. The data structure of claim 13 wherein one of the attributes comprises data indicating whether the document is a hidden document.

15. The data structure of claim 13 wherein one of the attributes comprises data indicating whether the document is a system document.

16. The data structure of claim 13 wherein one of the attributes comprises data indicating whether the document is a read only document.

17. The data structure of claim 9 wherein the second set of data includes data corresponding to a creation date of the document.

18. The data structure of claim 9 wherein the second set of data includes data corresponding to a last access date of the document.

19. The data structure of claim 9 wherein the second set of data includes data corresponding to expiration of the document.

20. The data structure of claim 9 wherein the second set of data includes data corresponding to a parent folder of a folder of the document.

21. The data structure of claim 20 wherein the second set of data includes data corresponding to attributes of the parent folder.