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

|Request For Comments Form | Technology Process FAQ | Request for Information FAQ |

Current OMG Technology Adoption Processes Under Way
Last updated: Tuesday, 31-Mar-2015 17:01:18 EDT

Specifications which have been approved by the OMG membership are available to everyone, but only OMG members have access to specifications under development. This page lists OMG Request processes for technology submissions which are open to both members and the general public for comment or response. For more information on the OMG technology adoption process, please see the Process Technology FAQ.

Please note that the actual Request documents are freely available; simply click on the document number below to get the document in several different formats. However, the internal mechanics of the OMG process are available only to members by clicking on the process name.

A catalog of our published specifications is available here. If you're interested in learning more about the OMG and the benefits of becoming a member, please contact our Business Development staff.

Pending Requests for Comments:

Automated Source Code CISQ Top 15 Performance Efficiency Measure RFC
Automated Source Code CISQ Top 15 Performance Efficiency Measure RFC clean (document admtf/2014-12-25)
Automated Source Code CISQ Top 15 Performance Efficiency Measure RFC inventory file (document admtf/2014-12-26)
Automated Source Code CISQ Top 15 Performance Efficiency Measure RFC inventory file (document admtf/2014-12-27)
CISQ Automated Source Code Performance Efficiency Measure RFC IPMSS.xmi (document admtf/2014-11-08)
CISQ Automated Source Code Performance Efficiency Measure RFC SMM.smm (document admtf/2014-11-09)
Cover Letter for admtf2014-11-07 CISQ Automated Source Code Performance Efficiency Measure RFC (document admtf/2014-11-10)

Automated Source Code CISQ Top 20 Maintainability Measure RFC
Cover Letter for admtf2014-11-12 CISQ Automated Source Code Maintainability Measure RFC (document admtf/2014-11-15)
Inventory for admtf/2014-12-16 Automated Source Code CISQ Top 20 Maintainability Measure RFC (document admtf/2014-12-20)
UPDATED Automated Source Code CISQ Top 20 Maintainability Measure RFC clean (document admtf/2014-12-16)
XMI for admtf/2014-11-12 Automated Source Code CISQ Top 20 Maintainability Measure SMM (document admtf/2014-12-19)
XMI for admtf/2014-12-16 Automated Source Code CISQ Top 20 Maintainability Measure SPMS (document admtf/2014-12-18)

Automated Source Code CISQ Top 29 Reliability Measure RFC
Automated Source Code CISQ Top 29 Reliability Measure RFC SPMS -- XMI file (document admtf/2014-12-13)
CISQ Automated Source Code Maintainability Measure RFC SMM.smm (document admtf/2014-11-14)
Cover Letter for admtf2014-11-01 CISQ Automated Source Code Reliability Measure RFC (document admtf/2014-11-04)
UPDATED Automated Source Code CISQ Top 29 Reliability Measure clean (document admtf/2014-12-11)
UPDATED Inventory for admtf/2014-12-11 UPDATED Automated Source Code CISQ Top 29 Reliability Measure (document admtf/2014-12-15)

IDL4.0 RFC cover letter (document mars/2015-01-04)
Updated IDL 4.0 RFC inventory file (document mars/2015-03-02)
Updated proposed IDL4.0 RFC (document mars/2015-03-01)

Pending Requests for Proposals:

Agent Metamodel and Profile (AMP) RFP (document ad/2008-09-05)
This Request for Proposal solicits submissions for an Agent Metamodel and Profile (AMP). Essentially, the AMP RFP requests a metamodel and profile for extending UML with capabilities applicable to agents and agent-based software. Submissions developed in response to this RFP will achieve the following: Clarify semantics concerned with modeling agents. Establish Agent modeling best practices utilizing OMG technologies. Develop a MOF-compliant agent metamodel to be used either standalone or via extending the existing UML metamodel with agent modeling capabilities. Enable agent model interchange between tools via XMI. Optionally facilitate modeling of Peer-to-Peer, Grid and Cloud computing, and other technologies in terms of a collection of Agents. It is expected that responses to this RFP will make good use of agent modeling capabilities already supported by the OMG.

Application Programming Interfaces (API) to Knowledge Bases (KB) RFP (document ad/2010-06-09)
The intent of this RFP is to request proposals for Application Programming Interfaces (API) to Knowledge Bases (KB). According to Wikipedia ([WIK-KB]), “a knowledge base is a special kind of database for knowledge management, providing the means for the computerized collection, organization, and retrieval of knowledge”. This RFP targets mainly the basic administration services as well as the retrieval and the modification of knowledge in a KB designed specifically for use with knowledge representation languages supported by OMG standards, including but not limited to those supported by the Ontology Definition Metamodel (ODM - Proposals are sought that create a common set of APIs and interfaces for accessing namespaces and IRIs (internationalized uniform resource identifiers), documents, and other common infrastructure, some of which is modeled, for example, in the ODM RDFWeb package of the RDF metamodel, regardless of the target representation language, for knowledge representation languages that can be serialized in XML. The primary target is for accessing such KBs in the context of a tool, such as a parser, ontology editor, inference engine, or other applications where a uniform set of APIs and related services is desirable. APIs and service interfaces supporting basic queries, such as those that can be represented in SPARQL, are also desired. While this API shall be independent from the way the KB was populated and how the KB is designed and organized, the resultant API(s) and services shall be designed to complement and work in concert with ODM. It is understood that this effort may necessitate modifications to the ODM, including collaboration with ODM revisions underway to support OWL 2. This RFP solicits proposals for the following: API to retrieve raw information from a KB (resources, properties…); API to modify raw information in a KB; API to query knowledge in a KB (i.e., through reasoning); API to create instances: API to administrate the KB: add, import or remove ontology

Archetype Modeling Language (AML) (A UML Profile for Modeling Archetypes) RFP (document health/2012-07-01)
The objective of this RFP is to provide a standard for modeling Archetype Models (AMs) using UML, to support the representation of Clinical Information Modeling Initiative (CIMI) artifacts in UML. Archetypes are Platform Independent Models (PIMs), which are developed as a set of constraints on a specific Reference Model (RM). This RFP solicits proposals for an UML Profile, to be known as the "Archetype Modeling Language" (AML). The AML Profile will be developed as an aggregation of three sub-profiles, which together meet the requirements of archetype modeling. The three sub-profiles of the AML Profile will include: - Reference Model Profile (RMP): This profile will enable the specification of reference models, upon which archetypes can be based. - Constraint Model Profile (CMP): This profile will support the specification of constraints on a given reference model, to enable the development of archetypes, including Clinical Information Models (CIMs). - A Terminology Binding Profile (TBP): This profile will support the binding of information models to terminology, with optional support for binding to CTS2. Terminology bindings will include:
1. Value Bindings: Linkage of the data model to value domains, which restrict the valid value of an attribute to a set of values that corresponds to a set of meanings recorded in an external terminology;
2. Semantic Bindings: Defining the meaning of model elements, using concepts in an external terminology; and
3. Constraint Bindings: Specifying constraints on the information model, using concepts and relationships defined in an external terminology. This set of three UML sub-profiles (which together constitute the AML) will enable the specification of CIMI clinical model content (using the CIMI Reference Model), and the generation of CIMI clinical model artefacts, such as the Archetype Definition Language (ADL). While the transformation of AML models to an instance of the Archetype Object Model v1.5 (AOM-1.5) is optional, this transformation must be possible. The Archetype Definition Language (ADL) is a serialization of the Archetype Object Model.

Coordination of Care Service (CCS) RFP (document health/2015-03-04)
The scope of this RFP is to define the functions or capabilities required for effective coordination of care. Recognizing that ongoing coordination of care is a collaborative activity between care team members, the Coordination of Care Service is intended to fill a void in communication that presently exists between systems and care stakeholders. This includes not only the "professional" care team, but extends to include the patient themselves and designated caregivers and family members as participants in the Care Team. Effective coordination of care involves care team collaboration, goal oriented care planning, care tracking, and interventional activities. This will include support for continual assessment and review. The ability of a care plan to support specialty care domains within the context of broader care planning is an essential feature, providing the ability to establish clinical contexts and support care planning for those contexts. This RFP will provide for the ability to: - Establish and maintain care team relationships across organizations and point-of-care systems - Enable the care team to contribute to a shared and dynamic care plan - Enable the care team to track changes through time - Enable the care team to communicate within the context of the care plan and the continuity of care record

Event Metamodel and Profile (EMP) RFP (document ad/2008-09-15)
This Request for Proposal solicits submissions for an Event Metamodel and Profile (EMP). Essentially, the EMP RFP requests a metamodel and profile for extending UML with capabilities applicable to the sensing and interpretation of events, such as monitoring, filtering, aggregation, and correlation. Submissions developed in response to this RFP will achieve the following: Clarify semantics concerned with modeling events. Establish Event modeling best practices utilizing OMG technologies. Develop a MOF-compliant event metamodel to be used either standalone or via extending the existing UML metamodel with event modeling capabilities. Enable event model interchange between tools via XMI. It is expected that responses to this RFP will make good use of event modeling capabilities already supported by the OMG

Hardware Abstraction Layer for Robotic Technology (HAL4RT) RFP (document robotics/2014-06-14)
This RFP is the first step towards standardization of the application programming interface to access hardware devices such as motors and sensors. Currently, porting existing software to different systems, including device drivers in the development of embedded systems, requires considerable effort. For example, turning on an LED or operating a motor on different hardware may require considerable effort because the application program interfaces to control sensors and motors are uniquely defined by the device manufacturers. It is necessary to unify these interfaces. A Hardware Abstraction Layer is an open platform to standardize the specifications of the software implementation of robotics and control systems. A Hardware Abstraction Layer provides the base portion of a software platform for robotics and control systems, and aims to enable applications to run on different hardware. This increases the portability and reusability of the software, resulting in improved quality, lower costs and improved productivity. It is expected to improve convenience for users and developers. This RFP solicits proposals for the specification of a Hardware Abstraction Layer as a solution to these problems. This will make the software more applicable to real robotic software development.

IEF Reference Architecture RFP (document mars/2014-03-17)
The Information Exchange Framework (IEF) is an OMG initiative to develop a family of specifications for policy-driven, data-centric information sharing and safeguarding (ISS) services. These services target the automation of key policy decision and enforcement points to enable responsible information sharing across a broad range of business and operational scenarios. This Request for Proposal (RFP) seeks submissions for an overall reference architecture, reference model, and supporting materials for the IEF. The IEF Reference Architecture (RA) will be used to steer the overall IEF effort and broaden general understanding of domain requirements. The domain focus of the IEF RA includes interagency information sharing, often challenged by rapid, unpredictable changes in operational contexts (e.g., threat, risk, roles & responsibilities, scale, scope, and severity), e.g.: 1. Military (coalition and Civilian-Military) operations; 2. National Security; 3. Public Safety; 4. Crisis Management; 5. Border Security; 6. Emergency Management; and 7. Humanitarian Assistance. The IEF is focused on these environments because they require higher degrees of flexibility, agility and adaptability: often more than traditional solutions can satisfy. This RFP solicits proposals for a reference architecture for the IEF comprising: o A Platform Independent Model (PIM) for the IEF; o At least one Platform Specific Model, associating PIM elements to applicable standards; and o Operating concept and use cases for the IEF.

Information Management Metamodel (IMM) RFP (document ab/2005-12-02)
This RFP solicits proposals for a standard metamodel to address the needs of Information Management. This includes the scope of the existing Common Warehouse Metamodel (CWM) standard but is extended to cover the following areas: · MOF2 Metamodel for Information Management (IMM) · UML2 Profile for Relational Data Modeling, with a mapping to the IMM metamodel and SQL DDL · UML2 Profile for Logical (Entity Relationship) Data Modeling, with a mapping to the IMM metamodel · UML2 Profile for XML Data Modeling, with a mapping to the IMM metamodel and XML Schema · UML2 Profile for Record Modeling, with a mapping to the IMM metamodel and COBOL Copybooks · A standardized ‘Information Engineering’ data modeling notation with a mapping to the IMM metamodel

MOF to RDF Structural Mapping in Support of Linked Open Data RFP (document ad/2009-12-09)
RDF and Linked Open Data (LOD) have become important technologies for exposing, managing, analyzing, linking and federating data and metadata. This set of RDF based technologies, sometimes known as the “Semantic Web” or “Web 3.0”, are emerging as the lingua franca of data on the web. Major initiatives such as the President’s open government initiative are moving to the use of RDF & Linked Open Data as the foundation for publishing all government data and metadata in support of transparency. OMG & MOF based models should be a part of the LOD and Web 3.0 data cloud. The objective of this RFP is to define a structural mapping between OMG-MOF models and RDF to provide for better integration of MDA and LOD, to enable the ability to apply LOD capabilities to MOF compliant models and to make the information available in MOF compliant models available as LOD web resources. Any MOF based model should be able to become a LOD resource.

Metamodel Extension Facility RFP (document ad/2011-06-22)
This RFP solicits proposals for a Facility for extending and integrating metamodels that will complement and may eventually replace the current UML Profiles capability. The new Facility will be: o Able to replicate all of the semantic capabilities of the current profile mechanism; o Applicable to any metamodel or well-formed metamodel subset, not just UML; o Defined in a technically sound manner; o Able to define new diagram mappings; o Integrated with OMG platform technologies.

OCL 2.5 RFP (document ad/2014-03-05)
Despite some limitations, OCL has proved useful in fleshing out the details of a variety of OMG specifications. However users regularly report a steep learning curve and poor useability. This RFP solicits proposals for the following: resolution of OCL misalignments with UML normative UML-aligned metamodels for OCL editorial revision of the OCL specification to align with its metamodels no incompatible changes to the OCL Concrete Syntax language improved useability

Ontology, Model and Specification Integration and Interoperability (OntoIOp) RFP (document ad/2013-12-02)
This RFP solicits proposals for the following: A specification for an abstract metalanguage with an associated metamodel targeted at cross-language interoperability among a class of concrete languages used to record logical expressions found in ontologies, models and specifications. A list of concrete languages and translations to be recognized and correctly processed by implementations of this specification. A description of constraints and conformance criteria for additional concrete languages and translations between concrete languages that are not explicitly supported, but nonetheless have equivalent uses that could be recognized and correctly processed by implementations

Precise Semantics of UML State Machine RFP (document ad/2015-03-02)
The objective of this RFP is to solicit specifications containing more precise semantics for UML state machines to enable execution, allow model checking, and reduce ambiguities in UML models. By semantics we mean the underlying meaning of models, that is, the constraints that models place on the structure and runtime behavior of the specified system. In support of this objective, the RFP solicits proposals for the precise specification of the behavioral semantics for the metaclasses supporting the modeling of state machines in UML. Proposals shall build on the precise semantics of Foundational UML (fUML), which specifies the execution semantics of a computationally complete and compact subset of UML 2 to support execution of activities, and be consistent with the Precise Semantics of UML Composite Structures (PSCS).

RIA Dynamic Component Model RFP (document mars/2013-03-28)
The Rich Internet Application (RIA) domain provides client-side functionalities like visualization, user interactions, and device control for internet-based distributed applications. Usually, a RIA Application is rendered with a RIA runtime engine (referred to as a RIA Platform), which behaves like a typical application or native component. In an Enterprise business application, master data like product codes or basic data like order information are retrieved and/or referenced frequently by all subsequent applications. To increase the reusability of applications, front-end RIA Applications should be componentized as server-side/back-end distributed business components such as EJB, OSGi, and CCM. Moreover, this RIA componentization should be done under no-compilation (XML and JavaScript) and runtime deployment environment (no pre-installation, e.g., HTML) conditions so that a RIA Application can be treated as a RIA Component by another RIA application. This RFP solicits proposals for the following: o A standard RIA Dynamic Component Model (RDCM) which defines the services necessary to dynamically construct a RIA Application using RIA Components specific to a single, homogenous RIA Platform. The goal is a specification defining a format for declaring interfaces for exposing properties and methods within the RIA Application, as well as, how to use interfaces at development time and/or runtime in a RIA Platform. Submissions developed in response to this RFP should address the following: o A Vocabulary defining a RIA Component interface. This vocabulary defines the terminology used in the RIA development community including event information, property, method, and event handler. o A Platform Independent Model (PIM) of the component model which maps the preceding vocabulary including: o Mechanisms for the dynamic deployment of RIA Components, consisting of interface descriptions (IDL) and implementations (RIA Application source code). o Mechanisms for dynamically instantiating implementations and dynamically binding interfaces while executing a RIA Application. o Mechanisms for calling interfaces and exchanging data including dynamically declared custom data types. o Platform Specific Models (PSM) implementing the preceding PIM for specific deployment platforms, including JavaScript. The RDCM RFP does not apply to: o Presentation issues (layout and look & feel) of a RIA Application. o Specifications addressing bi-dimensional and tri-dimensional computer based graphics. o Instantiations of RIA runtime engines based on an OS application or native component. o Data exchanged between RIA runtime engines. o Server-side/back-end web applications.

Semantic Information Modeling for Federation (SIMF) RFP (document ad/2011-12-10)
The SIMF RFP asks for submissions for a standard that addresses the federation of information across different representations, levels of abstraction, communities, organizations, viewpoints, and authorities. Federation, in this context, means using independently conceived information sets together for purposes beyond those for which the individual information sets were originally defined. The purpose of SIMF is to help federate information across different authorities, vocabularies and formats. Current conceptual and logical information modeling approaches tend to be focused on a particular information modeling problem, using a particular technical approach. Examples of such technical approaches include object modeling, DBMS modeling and exchange schema modeling. SIMF seeks to address the problem of information federation by specifying standards for conceptual domain modeling, logical information modeling and model bridging relationships. SIMF submissions will define, adopt and/or adapt languages to express the conceptual domain models, logical information models and model bridging relationships needed to achieve this federation. Many if not all of these capabilities can be achieved with expert application of multiple standards and technologies. SIMF is intended to unify and tailor these capabilities, providing a standard for tools that reduce the barrier to entry and overhead required to achieve federated information.

TACSIT Data Exchange RFP (document c4i/2015-03-20)
The domain of military and operational Command and Control systems is characterized by a huge variety of underlying computing platforms. A standard based interface to common TACtical SITuation (TACSIT) services is thus essential for interoperable and open systems. In this scope, a first standard has already been issued by the OMG: the TACSIT Controller Interface consists of a set of interfaces to interact with TACSIT display systems. This RFP solicits now proposals for data interfaces to TACSIT systems. More specifically, it requests: • The standardisation of the data that need to be exchanged with TACSIT systems; • The standardisation of the interfaces needed to exchange data from/to TACSIT systems.

UML Operational Threat & Risk Model RFP (document sysa/2014-06-17)
In the broadest sense, organizations manage threats and risks in order to provide a systematic response to uncertainties and enhance situational awareness. Multiple communities have developed data and exchange schema and interfaces for sharing information about threats, risks and incidents that impact important government, commercial and personal assets and privacy. While each of these schema and interfaces provides value for a specific community it is difficult to federate these multiple representations to arrive at broad-based planning, simulation, assessment, situational awareness and forensics, and to then enact the appropriate courses of action. Cyber related attacks have added a new dimension that stresses traditional assessment, monitoring and mitigation strategies. This RFP calls for a conceptual model for operational threats and risks that unifies the semantics of and can provide a bridge across multiple threat and risk schema and interfaces. The conceptual model will be informed by high-level concepts as defined by the Cyber domain, existing NIEM domains and other applicable domains, but is not specific to those domains. This will enable combined Cyber, physical, criminal and natural threats and risks to be federated, understood and responded to effectively. Out of scope for this RFP is non-operational business relevant risk such as marketplace risk, credit risk, legal risk, project management risk, etc. The conceptual model will have an information exchange format based on NIEM and an explicit mapping to STIX . Other exchange formats, such as CAP may be supported as well.

UML Profile for NIEM 3 (NIEM-UML) RFP (document gov/2014-03-01)
This Request for Proposal (RFP) solicits proposals related to developing the next major revision of the OMG Unified Modeling Language (UML) Profile for the National Information Exchange Model (NIEM) Specification, which is commonly referred to as NIEM-UML. The revision addresses alignment to the newest version of NIEM, i.e. NIEM Version 3. Specifically, it addresses changes to the NIEM content model and the technical architecture. NIEM-UML allows modelers and developers to produce NIEM model packages conforming to the NIEM Naming and Design Rules (NDR) and the Model Package Description (MPD) Specification. The profile was created to broaden NIEM adoption by facilitating the separation of concerns between community business needs and XML Schema specific technology implementations. The OMG adopted the UML Profile for NIEM (based on NIEM Version 2.1) in December 2013. The profile has been successfully implemented in both commercial and open source development platforms. Due to the extensive changes to NIEM between Versions 2.1 and 3, revisions are outside the scope of a Revision Task Force (RTF). This RFP for a major revision solicits proposals for the following: o UML profiles for modeling NIEM MPDs; a logical profile that will enable the development of Platform Independent Models for NIEM content and a second profile that models MPD metadata and provides the parameters required to transform the logical model to NIEM-conformant XML schema and MPD specifications (the Platform Specific Model). o A transformation from UML models that conform to the NIEM profiles (described above) to NIEM-conformant MPD artifacts. o Optionally, a transformation from a NIEM-conformant XML schema set (as defined by the NIEM NDR) to a UML model that conforms to the profile(s). o A UML representation of the NIEM controlled vocabularies (reference namespaces) from which MPDs are constructed. This UML representation must conform to the profiles mentioned in the first bullet point.

UML Testing Profile V2 (UTP2) RFP (document ad/2013-12-08)
This RFP solicits proposals for the following: a UML Testing Profile as a successor specification of the UML Testing Profile 1.2 a UML Testing Profile that is applicable to a variety of domains and methodologies a UML Testing Profile enables the specification of test cases for different quality attributes and on different level of abstractions a UML Testing Profile that allows for test generation and the precise specification of test coverage

UML® Profile for ArchiMate® and ArchiMate® Meta-model RFP (document bmi/2014-12-03)
ArchiMate® is a visual design language developed by The Open Group®. It is intended to enable the description of enterprise architecture domains and their relationships and dependencies. The ArchiMate language has been used to describe portfolios of software products and components in a way akin to how a Computational Independent Model (CIM) is used in an implementation of Model Driven Architecture® (MDA®). More detailed models that would conceptually correspond to Platform Independent Models (PIM) and Platform Specific Models (PSM) are better described using UML®, BPMN, and other specifications developed by the Object Management Group® (OMG®). This specification is intended to facilitate that development approach by creating a UML Profile for ArchiMate and a MOF® meta-model of ArchiMate, thus enabling ease of use of Archimate in combination with UML, BPMN and other OMG modelling language specified in MOF, in the same tool. This RFP solicits proposals for the following: o A UML Profile for ArchiMate o A MOF Meta-model of ArchiMate

UPDM 3.0 RFP (document c4i/2013-09-11)
Architecture frameworks continue to evolve. A NATO Architecture Capability Team (Architecture CaT) meeting on Sept. 10-11, 2012 committed to moving to a single world-wide Architecture Framework. Consequently, a new architecture framework profile supporting a unified nations' framework is needed. This RFP solicits proposals for the following: An architecture framework UML profile that reuses SysML V1.3, where appropriate, that evolves from legacy architectural frameworks including but not limited to the Ministry of Defence Exchange Mechanism [MODEM], DoDAF 2.x Metamodel (known as [DM2]), and the International Defence Enterprise Architecture Specification [IDEAS]. The proposed architecture framework profile shall enable the development of an integrated Architecture Description (AD).

Unified Component Model for Distributed, Real-Time and Embedded Systems RFP (document mars/2013-09-10)
The objective of this RFP is to solicit proposals for a new component model called the “Unified Component Model” targeting Distributed, Real-Time and Embedded (DRTE) Systems. A component model defines a set of standards for component implementation, naming, interoperability, customization, composition, evolution, and deployment [COMP]. The UCM will be a simple, lightweight, middleware-agnostic, and flexible component model. The UCM will allow many different interaction models, including publish-subscribe and request-reply.

Current Specification Revision Processes (available to members only:

Action Language for fUML 1.1 (ALF) RTF
Application Instrumentation 1.0 FTF 2
Automated Source Code CISQ Top 15 Performance Efficiency Measure 1.0 FTF
Automated Source Code CISQ Top 21 Maintainability Measure 1.0 FTF
Automated Source Code CISQ Top 29 Reliability Measure 1.0 FTF
Automated Source Code Security Measure (ASCSM) 1.0 FTF
Common Terminology Services 2 (CTS2) 1.3 Revision Task Force
DDS Security 1.0 FTF 2
DDS-PSM-Cxx v1.1 RTF
DDS-PSM-Java v1.1 RTF
DateTime Vocabulary (DTV) 1.2 RTF
DateTime Vocabulary (DTV) 1.3 RTF
Decision Modeling and Notation 1.1 RTF
Dependability Assurance Framework for Safety-Sensitive Consumer Devices (DAF) 1.0 FTF
Diagram Definition 1.2 RTF
Essence 1.1 RTF
FIBO Business Entities 1.0 FTF 2
FIBO Foundations 1.1 RTF
FIBO Indices and Indicators 1.0 FTF
Financial Industry Global Identifier (FIGI) 1.0 FTF
Finite State Machine Component for RTC (FSM4RTC) 1.0 FTF
Ground Equipment Monitoring Service 1.4 RTF
IDL to C++11 1.2 RTF
IDL to C++11 1.3 RTF
Information Exchange Packaging Policy Vocabulary (IEPPV) 1.1 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
Precise Semantics of UML Composite Structures 1.0 FTF
RPC over DDS 1.0 FTF
Records Management Services V1.1 (RMS) RTF
Requirements Interchange Format V1.2 (ReqIF) RTF
Robotic Interaction Service Framework 1.1 RTF
Ruby CORBA Language Mapping 1.3 (RCLM) RTF
SoaML 1.1 RTF
Structured Metrics Metamodel 1.1 RTF
Structured Metrics Metamodel 1.2 RTF
Structured Patterns Metamodel Standard (SPMS) 1.1 RTF
SysML 1.5 RTF
TelcoML 1.1 RTF
TestIF 1.1 RTF
UML Profile for BPMN Processes 1.1 RTF
Vector Image Signal Processing Specifications 1.6 RTF
Web-enabled DDS 1.0 FTF 2
XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF
fUML 1.2 RTF
Copyright © 1997-2015 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact
For TECHNICAL questions, please contact
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