OMG Homepage MDA Homepage CORBA Homepage MOF Homepage UML Homepage CWM Homepage XMI Homepage DDS Homepage OMG MARTE BPMN Homepage SysML Homepage banner
 


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 Terminology Services 2  (CTS2)
Description: Structured terminologies provide a foundation for information interoperability by improving the effectiveness of information exchange. They provide a means for organizing information and serve to define the semantics of information using consistent and computable mechanisms.

Terminologies are constructed to meet scope specific domain requirements. The domain specific nature of structured vocabularies often leads to variation in design patterns across the available terminology space. The ability to provide consistent representation and access to a broad set of terminologies enables multiple disparate terminology sources to be available to a community, and helps to ensure consistency across the domain space of that community. Service interfaces to structured terminologies should be flexible enough to accurately represent a wide variety of vocabularies and other lexically-based resources.

The PIM specified in this document for CTS 2 is intended to mediate among disparate terminology sources by providing a standard service information and computational model. The Information Model specifies the structural definition, attributes and associations of Resources common to structured terminologies such as Code Systems, Binding Domains and Value Sets. The Computational Model specifies the service descriptions and interfaces needed to access and maintain structured terminologies.
Finalization Information:
Status: 1.0 finalization underway Working Document: 
FTF Beta 1
See also Specifications Page

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:
Current version: 1.1 Past versions
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:
  Analysis & Design PTF        
Related OMG Specifications: CWM, UML
Most recent IPR and Implementation questionnaire responses:

Specification Name: Concrete Syntax for UML Action Language [Action Language for Foundational UML] (ALF)
Description: This specification is a textual surface representation for UML modeling elements. The execution semantics for ALF are given by mapping the ALF concrete syntax to the abstract syntax of the standard Foundational Subset for Executable UML Models (known as foundational UML or fUML).
Finalization Information:
Status: 1.0 finalization underway Working Document: 
FTF Beta 1
Contact: ALF FTF

Specification Name: Diagram Definition (DD)
Description: This specification provides a basis for modeling and interchanging graphical notations, specifically node and arc style diagrams as found in UML, SysML, and BPMN.
Finalization Information:
Status: 1.0 finalization underway: Working Document: 
FTF Beta 2
Contact: Diagram_Definition_FTF

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:
Current version: 2.4.1 Past versions
Revision Information:
Status: 2.1 revision underway  Working Document: Version 2.0 Contact: MOF 2.0 Core RTF
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 Driven Message Interoperability (MDMI)
formerly known as Conversion Models for Payment Message Standards)
Description: Provides a declarative, model driven mechanism to perform message transformation - not only to handle the movement of data between different message formats, but also to create a versioning mechanism so that new version of a message can be mapped to older version, thereby reducing the barriers that prevent the introduction of new versions of messages and greatly reducing the cost of change.
Keywords: Autonomy, Business analyst, Business Element ,Business rule, Composition, Conversion Rule, Datatype,  Domain,  Domain Data Dictionary, Domain Repository, Entity, Environment, Federated dictionary, Federate, Group, Keyword List,  Leaf Format, Leaf Format Expression, Language, Location, Location Expression, Language,  Leaf Syntax Translator,  Message Element, Message Element Relationship Model,  Message Composite, Message format, Message Group, Message Element Set, Message Model,  Message Syntax Model, Message Syntax Translator, MSxx, MTxx,  Near Synonym, Node ID, Physical Message Instance, Qualified Business Element, Qualifier  Runtime Application, Semantic Element, Semantic Map, Simple Message Composite, Synonym, TCxx,  Technical analyst, Type, UNIFI, Wire format
Latest/Past specifications:      Current version: 1.0                                    Past versions:  n/a
Most recent IPR and Implementation questionnaire responses:   

Specification Name: Model-level Testing and Debugging (MLTD)
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:
Status: 1.0 finalization underway Working Document: 1.0 Beta 1 Specification Contact: Model-level Testing and Debugging FTF
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 (MOFFOL)
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
Latest / past specifications:
Current version: 2.0 Past versions: n/a
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
Contact Information:
  Analysis & Design PTF        
Related OMG Specifications: MOF, OCL, QVT, UML Superstructure
Most recent IPR and Implementation questionnaire responses:    
 
Specification Name: MOF� Query / View / Transformation (QVT)
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.1 Past versions: 1.0
Revision Information:

Contact: QVT 1.2 RTF

Related OMG Specifications: MOF, OCL
Most recent IPR and Implementation questionnaire responses:

Specification Name: MOF� Support for Semantic Structures (SMOF)
Description: The Meta Object Facility (MOF) has proven itself as a valuable and powerful foundation for a family of modeling languages such as UML, ODM, CWM, etc. However, MOF 2 suffers from the same structural rigidity as many object-oriented programming systems, lacking the ability to classify objects by multiple metaclasses, the inability to dynamically reclassify objects without interrupting the object lifecycle or altering the object's identity and a too constrained view on generalization and properties. This extension to MOF modifies MOF 2 to support dynamically mutable multiple classifications of elements and to declare the circumstances under which such multiple classifications are allowed, required, and prohibited. This specification is part of the MOF 2 specifications. As such, it does not contain a complete specification of the Meta Object Facility version 2, but an increment to extend the MOF 2 Core with features to handle semantic structures. 
Finalization Information:
Status: 1.0 finalization underway Working Document: 
FTF Beta 1
Contact: SMOF FTF

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
Related OMG Specifications: MOF, SPEMXMI
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.

Latest / past specifications:

Current version: 2.3.1

Past versions: 2.2

Related OMG Specifications: MOF, UML, XMI
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.  
Latest / past specifications:

Current version: 1.3 (Beta 2)

Past versions: 1.2

 
Practitioner Certification:
OCSMP (OMG-Certified Systems Modeling Professional)

http://www.omg.org/ocsmp/

 
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
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
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:
Analysis & Design PTF      
Related OMG Specifications: MOF, UML, W3C XML, XMI
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.
Latest / past specifications:
Current version: 1.0 Past versions: n/a

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.
Latest / past specifications:
Current version: n/a Past versions: n/a
Finalization  Information:
Working Document: Version 1.0 Beta 2  
 

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:
Current version: 2.0 Past versions
Related OMG Specifications: UML, XMI
Most recent IPR and Implementation questionnaire responses:

Specification Name: Systems Modeling Language (SysML)
  See above:  Omg Systems Modeling Language (SysML)

Specification Name: SysML-Modelica Transformation (SyM)
Description: The SysML is a standardized graphical modeling language for capturing complex system descriptions in terms of their structure, behavior, properties, and requirements. Modelica is a standardized general purpose systems modeling language for analyzing the continuous and discrete time dynamics of complex systems based on solving differential algebraic equations. 
Finalization Information:
Status: 1.0 finalization underway Working Document::
FTF Beta 2
Contact: SyM_FTF

Specification Name: Unified Modeling Language� (UML�)
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:
Current version (Infrastructure and Superstructure): 2.4.1
Past versions

NOTE:  Version 2.0 does not have XSD or XML associated files due to structural problems with the UML metamodel.

Practitioner Certification:
OCUP (OMG-Certified UML Professional)

http://www.omg.org/ocup/

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.
Latest / past specifications:

Current version: 1.0

Past versions: n/a

Related OMG Specifications: MOF, UML, XMI
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:
  Analysis & Design PTF      
Related OMG Specifications: UML, UML Profile for CORBA, UML Profile for EDOC, MOF, XMI
Most recent IPR and Implementation questionnaire responses:

Specification Name: MOF 2 XMI Mapping  (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:
Current versions: 2.4.1 Past versions
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/27/2014Hit Counter

 

 
Copyright © 1997-2014 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact [email protected].
For TECHNICAL questions, please contact
[email protected]
.
This site is best viewed with Mozilla Firefox or Internet
Explorer versions 6.0 or later or any browser capable of viewing JavaScript and CSS 2.0. The site is using
DHTML JavaScript Menu By Milonic.com.