Bekim Demiroski - Redmond WA, US Robert T. Whitney - Seattle WA, US J. Patrick Thompson - Seattle WA, US Anil K. Nori - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707101, 707102, 707103 R
Abstract:
By modeling real-world application objects with complex structures, behaviors, and operations described by a schema which is enforced by the hardware/software interface system, various embodiments of the present invention provide rich sub-typing functionality by extending Items (and Item types) using “Extensions” which provide additional data structures (Properties, Relationships, etc. ) to already existing Items type structures. Extensions are strongly typed instances that cannot exist independently and must be attached to an Item or a Nested Element. Extensions are also intended to address “multi-typing” issues by enabling the overlap of type instances (e. g. , a Document may be a “legal document” as well a “secure document”).
Systems And Methods For Extensions And Inheritance For Units Of Information Manageable By A Hardware/Software Interface System
Bekim Demiroski - Redmond WA, US Robert T. Whitney - Seattle WA, US J. Patrick Thompson - Seattle WA, US Anil K. Nori - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707101, 707102, 707103 R
Abstract:
By modeling real-world application objects with complex structures, behaviors, and operations described by a schema which is enforced by the hardware/software interface system, various embodiments of the present invention provide rich sub-typing functionality by extending Items (and Item types) using “Extensions” which provide additional data structures (Properties, Relationships, etc. ) to already existing Items type structures. Extensions are strongly typed instances that cannot exist independently and must be attached to an Item or a Nested Element. Extensions are also intended to address “multi-typing” issues by enabling the overlap of type instances (e. g. , a Document may be a “legal document” as well a “secure document”).
Systems And Methods For Extensions And Inheritance For Units Of Information Manageable By A Hardware/Software Interface System
Bekim Demiroski - Redmond WA, US Robert T. Whitney - Seattle WA, US J. Patrick Thompson - Seattle WA, US Anil K. Nori - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707790, 707791, 707802
Abstract:
By modeling real-world application objects with complex structures, behaviors, and operations described by a schema which is enforced by the hardware/software interface system, various embodiments of the present invention provide rich sub-typing functionality by extending Items (and Item types) using “Extensions” which provide additional data structures (Properties, Relationships, etc. ) to already existing Items type structures. Extensions are strongly typed instances that cannot exist independently and must be attached to an Item or a Nested Element. Extensions are also intended to address “multi-typing” issues by enabling the overlap of type instances (e. g. , a Document may be a “legal document” as well a “secure document”).
Michael E. Deem - Redmond WA, US Michael J. Pizzo - Bellevue WA, US John Patrick Thompson - Seattle WA, US Denise L. Chen - Bellevue WA, US Alexander Vaschillo - Redmond WA, US Bekim Demiroski - Redmond WA, US Srinivasmurthy P. Acharya - Sammamish WA, US Robert T. Whitney - Seattle WA, US
A programming interface for a computer platform can include various functionality. In certain embodiments, the programming interface includes one or more of the following groups of types or functions: those related to core file system concepts, those related to entities that a human being can contact, those related to documents, those common to multiple kinds of media, those specific to audio media, those specific to video media, those specific to image media, those specific to electronic mail messages, and those related to identifying particular locations.
Anil Kumar Nori - Redmond WA, US Bekim Demiroski - Redmond WA, US Gregory S. Friedman - Redmond WA, US Michael B. Taylor - Seattle WA, US Michael E. Deem - Redmond WA, US Michael J. Newman - Redmond WA, US Michael J. Pizzo - Bellevue WA, US Nigel R. Ellis - Redmond WA, US Sanjay Nagamangalam - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 7/00
US Classification:
707807
Abstract:
The subject innovation provides a system and/or a method that facilitates developing schemas for a file storage system. A type definition component can provide a schema grammar, wherein a generator component can employ the schema grammar to build the schema for the file storage system. The schema grammar can describe information types stored in the file storage system that are represented as instances of complex types that are part of a type system that supports inheritance. The schema grammar can support a declaration of an association between types, versioning specifications, and/or content indexing specifications.
Mapping Of A File System Model To A Database Object
Nigel Ellis - Redmond WA, US Gregory Friedman - Redmond WA, US Bekim Demiroski - Redmond WA, US Anil Nori - Redmond WA, US Amit Shukla - Redmond WA, US Srinivasmurthy Acharya - Sammamish WA, US Jeffrey Pearce - Sammamish WA, US Michael Newman - Redmond WA, US Jason Hunter - Redmond WA, US
International Classification:
G11C 16/04
US Classification:
365185010
Abstract:
The subject invention provides a system and/or a method that facilitates mapping a data base model to a database object. A type storage system can utilize a storage mapping of a file storage data model. The mapping can describe the database object created based at least in part upon a schema and how instances of the type described in the schema are stored and/or accessed. Furthermore, a query can be provided to find at least one of an item, a document, and/or a contact that satisfy at least one criterion. The type storage system can receive data, wherein the data is at least one of a schema, a data model, a type, a query, and query criteria via an interface to provide the storing and querying. Additionally, the type storage system can generate a view that exposes at least one instance of the type.