[This is prerelease documentation and is subject to change in future releases. Blank topics are included as placeholders.]
This topic describes the system-provided models available in the code name “Oslo” repository, the application feature areas they describe, and when they are typically used in the design, development, and management processes. For more information about viewing domains and data instances in the Microsoft code name “Quadrant”, see "Quadrant".
Domains Provided with “Oslo”
The power and flexibility of a model-based development platform increases tremendously each time more of the models you need and want to use become available. The code name “Oslo” repository comes with a set of domain models written in the Microsoft code name “M” modeling language that are organized into modules (similar to namespaces in other languages) that help domain and model developers where to find the structures or functionality that they need. Models can:
- Represent specific items, such as .NET Framework metadata.
- Represent a specific pattern that you can use to shape your own models.
- Represent a specific pattern that you can use to indicate how the models should be projected and what features they should have.
These domains, which represent various architectural and feature areas, are stored as SQL schemas (the models themselves) and as data instances (your configured versions of models) in the “Oslo” repository and contain models in the following categories. The models are delivered as image files with the extension .mx and are installed in the “Oslo” repository during setup. The source files in “M” are also provided for reference purposes. Once installed, content can be explored either in SQL Server 2008 or in “Quadrant”.
Modules
-
Base Domain Library (BDL). This domain set (which consists of the Repository Schema, Repository.Item Schema, and System.Globalization Schema modules in “M” – SQL schemas in the “Oslo” repository) contains models that you can use to support the separation of logical data access (views, in SQL Server 2008) from physical storage (tables); establish Folders, which can be used to secure data access and version schemas and data; establish efficient ID patterns for data; support globalization; and control auditing and other security features in SQL Server 2008. The BDL defines storage extents and utilities for several commonly occurring kinds of data that can be referenced from other domains as well as a set of domain-neutral types and functions that can be incorporated into the definition of other domains. The image file is Repository.mx.
-
System_Runtime. The common language runtime (CLR) domain targets the Microsoft implementation of the ECMA CLI specification. It contains the schema of the metadata of a .NET Framework assembly and is installed as the System_Runtime SQL schema. With the CLR loader (LoadAssembly.exe) that is also provided with the “Oslo” SDK, you can load metadata from your own .NET assemblies into the code name “Oslo” repository to examine .NET metadata across a product, a division, or potentially an entire enterprise. The image file is System.Runtime.mx.
-
Microsoft.Uml2. The Microsoft.Uml2 domain targets the Object Management Group’s Unified Modeling Language™ (UML™) specification version 2.1.2; it is installed as the Microsoft.Uml2 SQL schema. UML 2.1.2 models in the Object Management Group’s XML Metadata Interchange (XMI) version 2.1 file format can be imported into the code name “Oslo” repository with the UML loader (
LoadUml.exe) that is included with code name “Oslo” modeling technologies. The UML model is work-in-progress that shows approach and direction; it is not a complete implementation of the UML specification. The image file is Microsoft.UML212.mx.
-
System.Identity. The System.Identity module exists to support applications such as directories which are concerned with storing, searching, and retrieving information (called claims) about physical and digital subjects and resources that can be uniquely identified. At the highest level, the
System.Identity schema is about entities called
Parties that have
PartyToPartyRelationships.
Parties include
People,
Organizations,
Groups,
Devices, and
Software Services. There are also special relationships called
Roles
that one party can play for another.
Parties
and
Roles
have
IdentityKeys, or unique names in multiple dimensions issued by
Authorities
and described in
Tokens. They also have (potentially multiple)
Locations.
Parties
access
Resources
according to
Policies. The instances in all these
Extents
can be specialized through a system of
Kinds. In addition,
Parties
can be arbitrarily extended without schema changes through
PartyAttributes. Since information about physical and digital subjects transcends conventional use in directory applications, federating subject and claim information to the
code name “Oslo” repository
is an important goal.
-
Language.Catalog. The Language.Catalog module represents a structured representation of an “M” program, also called the “M” semantic graph. The schema for the catalog is written in “M”, and the compiler can generate instances of a “M” program into that schema.
See Also