Microsoft Technology Licensing, LLC

Microsoft Corporation

Keith W Short

Mark H Lucovsky

Amit Mital

Joseph D Belfiore

Eric D Rudder

David G Campbell

Tandy Woodson Trower, Ii

Steven M Cellini

Steve Capps

Kaviraj Singh

Vivek Gundotra

Peter M Spiro

Charles T Fitzgerald

David Vaskevitch

Anthony Christopher Bloesch

William E Gibson

Dennis W Minium

Paul A Maritz

Kim Cameron

Andrea Westerinen

Tandy W Trower, Ii

Paul Martiz

One or more model elements may be extracted from a model. Coding patterns may be generated based on the extracted model elements. The coding patterns may be translated into statements, such as Structured Query Language (SQL) statements, which may be executed to instantiate at least a portion of a database. The database may be used to store, edit and/or query data that is arranged according to the model. The model may define a modeling language specification, such that the stored data may define various models that comply with the modeling language specification. Accordingly, the database may be queried to analyze the contents of the modeling-language compliant models.

Databases from models

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

One embodiment may be practiced in a computing environment and includes method acts for creating a new component model from an existing component model. The method includes accessing an existing component definition. The existing component definition is included in an existing component schema, which includes definitions of configuration parameters defined for the existing component including defining that one or more parameters are further configurable. Definitions of the one or more parameters that are defined as being further configurable are refined. The refined definitions for the one or more parameter values are stored in a refined schema defining refinements of the component definition, without including the existing component schema. The refined schema is stored separately from the existing component schema.

Modeling configurations of systems

The present invention extends to methods, systems, and computer program products for modeling party identities in computer storage systems. A federated identity fabric models identity data and relationships between portions of indentify data in computer storage systems in accordance with a uniform schema. The federated identity fabric can federate distributed identity and identity relationship data from computer storage systems within the variety of different computing environments. Code and metadata at computing environments associated with the federated identity fabric can interoperate to facilitate uniformly storing, accessing, modifying, deleting, and securing identity and identity relationship data within the federated identify fabric. Embodiments of the invention include utilizing an identity key table entry to locate party identity information and performing key transformations between different types of identity keys.

Modeling party identities in computer storage systems

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.

A server federation cooperatively interacts to fulfill service requests by communicating using data structures that follow a schema in which the meaning of the communicated data is implied by the schema. Thus, in addition to the data being communicated, the meaning of the data is also communication allowing for intelligent decisions and inferences to be made based on the meaning of the data. Cooperative interaction is facilitated over a wide variety of networks by messaging through a common API that supports multiple transport mechanisms. Also, mid-session transfer between client devices is facilitated by schema and the transport-independent messaging structure. The user interfaces of the client devices will appear consistent even if the client devices have different user interface capabilities.

Distributed computing services platform

Growing community of inventors

Redmond, WA, United States of America

Keith W Short