Microsoft Technology Licensing, LLC

Anthony Christopher Bloesch

Antony S Williams

Siddharth Jayadevan

James Randall Flynn

Donald F Box

Randy S Kimmerly

Haroon Ahmed

Arye Gittelman

Gunter Leeb

Keith W Short

William A Manis

Dennis W Minium

Ramesh Rajagopal

Lonny Bastien

Yordan Ivanov Rouskov

Murli D Satagopan

James Charles Kleewein

Titus Constantin Miron

Florian Voss

Vikrant Arora

Petru Moldovanu

Robert McKee Howard

Noaa Avital

Daniel Kershaw

Ji Liang

Dmitry Pugachev

Sriram Dhanasekaran

Jon Rosenberg

Yina Arenas

Marek Rycharski

Vijaya Manohararaj

Ozben Evren

Network services may include data associated with one or more entities. An aggregator service may host respective application programming interfaces (APIs) of the services at a single endpoint of the network such that the entities, including associations and relationships between entities, may be federated. For example, the services may register the entities of which the data of each of the services is associated with through a declarative entity model to establish an API schema for each of the services, which may be published at the aggregator service. In response to receipt of a request for entity related data from a client, the aggregator service may employ the declarative entity model to determine which of the services are associated with the entity related data such that a query may be submitted to the services, and how to aggregate responses to the query received from the services for transmission to the client.

Aggregation and federation of distributed service entities and associations

The present disclosure is directed to preserving running sessions during a side-by-side upgrade of system resources. Example aspects include deploying a first version and a second version of a system resource to a server within a network, the first version and the second version of the system resource both maintained within the system network and accessible via a version agnostic Application Programming Interface. Example aspects can receive, at a front-end server, a request for interaction with the system resource from a first client system, the request from the first client system including a header including version-identifying information. The systems and methods can determine, at a session version redirector, that the client system should be provided the first version and not the second version based on the version-identifying information in the header.

Preserving long running sessions during side-by-side upgrade

A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Metadata driven reporting and editing of databases

Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. Embodiments include a computer system receiving a database query including a request to edit one or more data items in the database. The computer system determines which data items would be affected by the requested data item edit. Based on the determination, the computer system accesses those data items that would be affected by the requested data item edit. The computer system retrieves metadata for each data item that would be affected by the requested data item edit. The metadata includes information at least partly indicating how the edit is to be performed. The computer system also performs the edit to affect the data items according to at least a portion of the retrieved metadata, regardless of how the edit would otherwise have been performed based on existing knowledge about the affected data items.

In one embodiment, a computer system generates a view of entities associated with varying data types for presentation on a generic viewer. The entities and data types have relationships as defined in a corresponding schema. The schema is stored as data in a repository with the data types. The computer system receives an edit request configured to change various selected entities, where each entity has an associated data type, queries the repository to determine various properties of the selected entities corresponding to the received edit request including the data type, and determines, based on the schema, that the edit is valid based on relationship information stored in the schema. The computer system also sends the validated edit information to the generic viewer for presentation. The generic viewer has no prior knowledge of how to handle the selected entities and corresponding data types.

Generic model editing framework

Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Generic editor for databases

Methods, systems, and computer program products are provided for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

Securing resource stores with claims-based security

Tables are created in such a way that allows rich querying using standard database routines and other tools. Developers and repository users are provided with a set of schema guidelines that describe how the software related items are to be categorized in the tables and how to use such tables for rich querying. For example, one such guideline provides for course-grained versioning of items (e.g., artifacts, metadata, etc.)&#x2014;as opposed to the fine grained object principle of unit change found in most repository systems such as the entity-property-value scheme. The developers or providers then use these guidelines to optimally categorize, in a natural way, their metadata and other software related items for storing copies thereof in the repository.

Easily queriable software repositories

In one embodiment, a computer system performs a method for providing repository item information from one or more different perspectives using virtual repository items within a customizable presentation scheme. A computer system accesses a user-defined presentation scheme that describes a manner in which repository items are to be presented. The computer system generates virtual repository items for actual repository items based on the user-defined presentation scheme. The virtual repository items are generated for presentation along with their actual repository items. The computer system maps the virtual repository items to different virtualized sets of repository items according to the user-defined presentation scheme. The virtualized sets comprise at least one of actual repository items and virtual repository items. The computer system presents the virtualized sets of repository items in one or more different perspectives within the user-defined presentation scheme.

Using virtual repository items for customized display

In one embodiment, tables are created in such a way that allows rich querying using standard database routines and other tools. This is accomplished by providing developers and repository users with a set of schema guidelines that describe how the software related items are to be categorized in the tables and how to use such tables for rich querying. For example, one such guideline provides for course-grained versioning of items (e.g., artifacts, metadata, etc.)&#x2014;as opposed to the fine grained object principle of unit change found in most repository systems such as the entity-property-value scheme. The developers or providers then use these guidelines to optimally categorize, in a natural way, their metadata and other software related items for storing copies thereof in the repository.

The present invention extends to methods, systems, and computer program products for partitioning modeling platform data. Embodiments of the invention facilitate partitioning modeling platform data into nested horizontal slices. Using nested horizontal slices makes the modeling platform data more manageable and permits modeling platform data to align with existing tools and processes. Schemas and tables can be used to partition modeling platform data vertically and folders can be used to partition modeling platform data horizontally. Thus, a user-interface can preset the intersection of folders and schemas/tables as navigable chunks of data compatible with existing tools and processes, such as, for example, software development tools.

Partitioning modeling platform data

The present invention extends to methods, systems, and computer program products for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

The present invention relates to a system and methodology providing an Application Programming Interface (API) and framework that supports a meta-object model for application design and operating system interactions. The API includes an input component that receives data and/or instructions. The input component processes a meta-data model that interrelates data via a class hierarchy, wherein the class hierarchy includes relationship descriptions between class objects, attributes, rules, and/or behavioral descriptions. Another aspect includes a data management system that includes a component to receive an item having meta-data annotations. An analysis component determines at runtime a structure for the item via deployment of the meta-data annotations. The system can also include a framework component that defines meta-data class derivations, meta-data classes, meta-data integrity rules, and/or meta-data class behavior.

Growing community of inventors

Vashon, WA, United States of America

Anthony Christopher Bloesch