Catalog of OMG Modeling and
Metadata Specifications
This page provides a catalog of OMG modeling specifications.
Specifications are listed alphabetically.
Description of Catalog Entries
Click here
for a description of each field for specifications catalogued below. coverage
Understanding Terms Used
In order to understand the various terms used to identify an OMG
specification as it moves through its editing cycles, consult the OMG
Specifications Tutorial.
|
| Specification Name: |
Common
Warehouse Metamodel (CWM™) |
| Description: |
Standard interfaces that can be used to
enable easy interchange of warehouse and business intelligence metadata
between warehouse tools, warehouse platforms and warehouse metadata
repositories in distributed heterogeneous environments. |
| Keywords: |
data warehouse, data mining, metadata,
record, repository, XML |
| Latest / past specifications: |
|
| Revision Information: |
|
| Related OMG Specifications: |
MOF, UML,
XMI |
| Related Industry Standards: |
ISO/IEC DIS 19504; ANSI SQL-92, MDC Open Information Model |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Common
Warehouse Metamodel (CWM™) Metadata Interchange Patterns (MIP) |
| Description: |
The purpose of this specification is to add a
semantic context to the interchange of metadata in terms of recognized
sets of objects or object patterns. It introduces the term "Unit of
Interchange" (UOI) to define a valid, recognizable CWM interchange.
From this information, a user of CWM, working in conjunction with CWM MIP,
should be able to produce truly interoperable tools. |
| Keywords: |
metadata interchange, patterns, pattern name,
pattern classification, Software Design Pattern, Unit of
Interchange (UOI) |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
CWM, UML |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Meta
Object
Facility (MOF™) |
| Description: |
MOF is an extensible model driven integration
framework for defining, manipulating and integrating metadata and data in
a platform independent manner. MOF-based standards are in use for
integrating tools, applications and data. |
| Keywords: |
metadata, meta-model, modeling |
| Latest / past specifications: |
|
| Associated documents: |
|
| Revision Information: |
|
| Related OMG Specifications: |
Components,
CWM, MOF QVT, MOF Versioning, UML, XMI |
| Related Industry Standards: |
ISO/IEC 19470:2005 |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Model-level
Testing and Debugging |
| Description: |
This
specification defines a platform independent model (PIM) of the interface
to an executing UML model for the purposes of testing and debugging. The
interface provides visibility into the model execution as well as a way to
provide test stimuli and collect test results. The interface assumes that
instrumentation code to support the interface is provided either manually
or through MDA transformations. The PIM contained in this specification is
independent of middleware and implementation language used. |
| Keywords: |
Built-In Self Test (BIST), instrumentation, system under
test (SUT), Test Instrumentation Interface (TII)
|
| Finalization Information: |
|
| Associated
documents: |
|
| OMG Cross Reference: |
Specialized
CORBA Specifications |
| Related OMG Specifications: |
MOF, UML |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
MOF
2.0 Facility and Object Lifecycle |
| Description: |
This specification separates out those
aspects of MOF related to communicating with and managing the
"facilities" responsible for providing the capabilities covered
by the other MOF specifications. These facilities may be at many different
levels, from a modeling tool to a full multi-user, multi-model repository.
The scope includes:• Locating and connecting to facilities; • Object
lifecycle operations (e.g. creation and deletion); and • Operational
aspects (e.g. transactions.) |
| Keywords: |
BaseFacility, BaseReadOnlyFacility, client, connection,
facility, outermost instance, resource adapter, stores, transactions,
versioning
|
| Finalization Information: |
|
| Associated
documents: |
|
| Related OMG Specifications: |
MOF, MOF
2 Versioning and Lifecycle, XMI |
| Related Industry Standards: |
Java
Metadata Interface (JSR 40), J2EE Connector Architecture Specification (JSR
112) version 1.5 |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
MOF Models to Text
Transformation Language |
| Description: |
This specification
addresses how to translate a model to various text artifacts such as code,
deployment specifications, reports, documents, etc. Essentially, it
addresses how to transform a model into a linearized text representation
using a template based approach wherein the text to be generated from
models is specified as a set of text templates that are parameterized with
model elements. |
| Keywords: |
block, escape
direction, macro, module, package, parameter, protected area block,
template, traceability, trace block, white space |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Associated
documents: |
|
| Contact Information: |
|
| Related OMG Specifications: |
MOF, OCL,
QVT, UML Superstructure |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
MOF™
Query / Views / Transformations |
| Description: |
This specification is one of a
series related to developing the 2.0 revision of the OMG Meta Object
Facility specification, referred to as MOF 2.0. This specification
addresses a technology neutral part of MOF and pertains to: 1.) queries on
models; 2.) views on metamodels; and 3.) transformations of models. |
| Keywords: |
Area, Bottom Pattern, Core
Domain, Core Transformation, Domain, Guard Pattern, Identifying Property,
Incremental Update, Key, Mapping (Core), Mapping Operation, Model Type,
Operational Transformation, Relation, Relational Transformation, Relation
Domain,Template Pattern, Trace Class, Trace Instance |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Revision Information: |
|
| Associated documents: |
|
| Related OMG Specifications: |
MOF, OCL |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
MOF™
2.0 Versioning and Development Lifecycle (MOFVD) |
| Description: |
The problem being addressed by this Specification is to
manage the co-existence of multiple versions of metadata in a Meta Object
Facility and their inclusion in different configurations (for example a
specific version of a PIM, the corresponding version of the derived PSM,
and the corresponding version of the generated system). |
| Keywords: |
class, context, dependencies, development lifecycle, extent,
history, package version |
| Latest / past specifications: |
|
Current version: 2.0 |
Past versions: n/a |
|
| Associated documents: |
|
| Revision Information: |
|
| Related OMG Specifications: |
MOF, SPEM, XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Object
Constraint Language (OCL) |
| Description: |
Specifies the Object Constraint Language (OCL), a
formal language used to describe expressions on UML models. These
expressions typically specify invariant conditions that must hold for the
system being modeled or queries over objects described in a model. Note
that when the OCL expressions are evaluated, they do not have side effects
(i.e., their evaluation cannot alter the state of the corresponding
executing system).
OCL expressions can be used to specify operations /
actions that, when executed, do alter the state of the system. UML
modelers can use OCL to specify application-specific constraints in their
models. UML modelers can also use OCL to specify queries on the UML model,
which are completely programming language independent. |
| Keywords: |
|
| Latest / past specifications: |
|
Current version: 2.2
|
Past versions: 2.0
|
|
| Related OMG Specifications: |
MOF, UML,
XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
OMG
Systems Modeling Language (SysML) |
| Description: |
The
OMG Systems Modeling Language (OMG
SysML™) is a general-purpose graphical modeling language for
specifying, analyzing, designing, and verifying complex systems that may
include hardware, software, information, personnel, procedures, and
facilities. In particular, the language provides graphical representations
with a semantic foundation for modeling system requirements, behavior,
structure, and parametrics, which is used to integrate with other
engineering analysis models. SysML represents a subset of UML 2.0 with
extensions needed to satisfy the requirements of the UML™
for Systems Engineering RFP. SysML uses the OMG XML Metadata Interchange (XMI®)
to exchange modeling data between tools.
|
| OMG Cross Reference: |
Domain
Specifications |
| Specification Name: |
Ontology
Definition Metamodel (ODM) |
| Description: |
This specification represents the foundation for an
extremely important set of enabling capabilities for Model Driven
Architecture (MDA) based software engineering, namely the formal grounding
for representation, management, interoperability, and application of
business semantics. ODM is applicable to knowledge representation,
conceptual modeling, formal taxonomy development and ontology definition,
and enables the use of a variety of enterprise models as starting points
for ontology development through mappings to UML and MOF. |
| Keywords: |
Complete MOF (CMOF), Common
Logic (CL), Computation Independent Model (CIM), Description Logics (DL),
Entity-Relationship (ER), Essential MOF (EMOF), interpretation, Knowledge
Interchange Format (KIF), PIM, PSM, RDF Schema (RDFS), Resource
Description Framework (RDF), Topic Maps (TM), traditional first order
logic, Web Ontology Language (OWL) |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Associated documents: |
|
| Revision Information: |
| Status: 1.1 revision underway |
Working Document: n/a |
Contact: ODM
1.1 RTF |
|
| Related OMG Specifications: |
MOF, OCL,
UML, XMI |
| Related Industry Standards: |
ISO/IEC
24707:2007 - Information technology - Common Logic (CL) - A framework
for a family of logic-based languages.
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39175 |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Reusable Asset
Specification (RAS) |
| Description: |
This Specification provides a set of
guidelines and recommendations about the structure, content, and
descriptions of reusable software assets. Recognizing that there are
different categories of reusable software assets, the specification
identifies some categories, or rather types or profiles, and provides
general guidelines on these profiles. RAS addresses the engineering
elements of reuse. It attempts to reduce the friction associated with
reuse transactions through consistent, standard packaging. |
| Keywords: |
application, archive, artifact, asset, component, consumer,
context, descriptor, DTD, harvest, idiom. metadata, package, pattern,
producer, profile, repository, reuse, scope, root, target,
variability point, workspace product |
| Latest / past specifications: |
|
Current version: 2.2 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
MOF, UML, W3C XML,
XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
|
Specification Name: |
Semantics
of a Foundational Subset for Executable UML Models (FUML) |
|
Description: |
The
Foundational UML Subset (fUML) is an executable subset of standard UML
that can be used to define, in an operational style, the structural and
behavioral semantics of systems.
It may also be used to define MOF-based modeling languages such as
standard UML or its subsets and extensions. For example, the semantics of UML
state machines can be specified as a program written in fUML. |
| Finalization
Information: |
Working Document:
FUML
1.0 Beta 2 Specification |
|
|
| Specification Name: |
Service
oriented architecture Modeling Language (SoaML) |
| Description: |
This specification presents the
SoaML (Service oriented architecture Modeling Language) specification
provides a metamodel and a UML profile for the specification and design of
services within a service-oriented architecture. |
| Finalization
Information: |
|
| Specification Name: |
Software Process
Engineering Metamodel (SPEM) |
| Description: |
This specification presents the Software
Process Engineering Metamodel (SPEM). This metamodel is used to
describe a concrete software development process or a family of related
software development processes. Process enactment is outside the scope of
SPEM, although some examples of enactment are included for explanatory
purposes. |
| Keywords: |
activity, assets, components,
DTD, lifecycle, metadata, meta-model, modeling, performer, process,
profile, role, step, work product |
| Latest / past specifications: |
|
| Associated documents: |
|
| Related OMG Specifications: |
UML, XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
Unified
Modeling Language™ (UML®) |
|
NOTE: Version 2.0 does not have XSD or XML
associated files due to structural problems with the UML metamodel.
|
| Description: |
A specification defining a graphical language
for visualizing, specifying, constructing, and documenting the artifacts
of distributed object systems. |
| Keywords: |
abstraction, action sequence, action state,
activity graph, architecture, association, class diagram, collaboration
diagram, component diagram, control flow, data flow, deployment diagram,
execution, implementation, pins, procedure. |
| Latest / past specifications: |
|
| Revision Information: |
|
| Related OMG Specifications: |
Diagram Interchange, OCL,
MOF, XMI |
| Related Industry Standards: |
UML 1.4.2 is available as ISO/IEC 19501;
19505 assigned to UML 2.1.2; ITU-T Recommendations Z.100 (SDL)
and Z.109 (SDL UML profile). |
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
UML
Diagram Interchange (UMLDI) |
| Description: |
This specification enables a smooth and seamless exchange
of documents compliant to the UML standard (referred to as UML models)
between different software tools. While this certainly includes tools for
developing UML models, it also includes tools such as whiteboard tools,
code generators, word processing tools, and desktop publishing tools.
Special attention is given to the Internet as a medium for exchanging and
presenting UML models. |
| Keywords: |
|
| Latest / past specifications: |
|
Current version: 1.0
|
Past versions: n/a
|
|
| Associated documents: |
|
| Related OMG Specifications: |
MOF, UML,
XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
UML Human-Usable Textual Notation
(HUTN) |
| Description: |
A specification for a
Human-Usable Textual Notation (HUTN) for expressing other specifications
in terms of the UML Profile for Enterprise Distributed Computing (EDOC)
and its companion UML Profile for CORBA. HUTN offers three main benefits.
(1.) It is a generic specification that can provide a concrete HUTN
language for any MOF model; (2.) The HUTN languages can be fully automated
for both production and parsing; and (3.) The HUTN languages are designed
to conform to human-usability criteria. |
| Keywords: |
base language, ECA, input stream, metamodel, output stream,
syntax |
| Latest / past specifications: |
|
Current version: 1.0 |
Past versions: n/a |
|
| Contact Information: |
|
| Related OMG Specifications: |
UML, UML
Profile for CORBA, UML Profile for EDOC, MOF,
XMI |
| Related Industry Standards: |
|
| Most recent IPR
and Implementation questionnaire responses: |
|
| Specification Name: |
XML
Metadata Interchange (XMI®) |
| Description: |
XMI is a model driven XML Integration
framework for defining, interchanging, manipulating and integrating XML
data and objects. XMI-based standards are in use for integrating tools,
repositories, applications and data warehouses. XMI provides
rules by which a
schema can be generated for any valid XMI-transmissible MOF-based
metamodel.
XMI provides a mapping from MOF to XML. As
MOF and XML technology evolved, the XMI mapping is being updated to comply with
the latest versions of these specifications. Updates to the XMI mapping
have tracked these version changes in a manner consistent with the
existing XMI Production of XML Schema specification (XMI Version 2).
|
| Keywords: |
abstract class, architecture, CDATA, class
diagram, composition, DTD, metadata, metamodel, modeling, production rules, schema,
XML |
| Latest / past specifications: |
|
| Revision Information: |
|
| Related OMG Specifications: |
UML, MOF
The following describes the relationship
between releases of XMI and releases of MOF:
XMI 1.1 corresponds to MOF 1.3
XMI 1.2 corresponds to MOF
1.4
XMI 1.3 (added Schema support) corresponds to MOF
1.4
XMI 2.0 (adds Schema support and changes document
format) corresponds to MOF
1.4
XMI 2.1 corresponds
to MOF 2.0
|
| Related Industry Standards: |
ISO/IEC 19503:2005; W3C DOM, EIA
CDIF, W3C SAX, Web-DAV, W3C XML |
| Most recent IPR
and Implementation questionnaire responses: |
|
[ top ]
[ Index
Page ]
Edited by Linda on
02/08/2010
|
|
|
|
