Pending Requests for Comments:
All OMG work in progress deadlines in chronological order
FACE Profile V2.0 RFC
The Open Group Future Airborne Capability Environment (FACE) Technical Standard is a set of guidelines for developing software applications that can be easily ported across different avionics systems. The Object Management Group (OMG) Unified Architecture Framework (UAF) is a modeling framework that provides a standard way to model, visualize, and analyze complex systems. Together, UAF provides a modeling framework for creating and analyzing system architectures that can be used to incorporate and/or guide the development of software components that comply with the FACE Technical Standard. At the System of System (SoS) Level, this profile may be used for acquisition across programs and platforms as well as to inform capability development. In order to support the new version of the FACE Technical Standard, a breaking change is needed, thus this FACE Profile v2.0 submission responds to the need for the FACE Profile for UAF v1.0 standard to be updated to support the latest version (edition 3.1) of the FACE Technical Standard from The Open Group.It also separates the loosely-coupled UML portion of the standard from the UAF extensions to enable development and use of FACE data architectures in both UML and SysML environments while preserving the option to further connect the FACE elements appropriately to UAF architectural elements. The update to FACE 3.1 and establishment of separability between UML and UAF in the standard were originally slated for a FACE Profile v1.1 Revision Task Force submission, but the result of the changes required would not have been backward compatible with the original specification. The breaking change prevented the work in the scope of the original task force, but because the updated FACE and related UDDL standard are publicly available, this RFC was created to combine the public information with the original FACE Profile for UAF v1.0.
FACE Profile 2.0 RFC
FACE Profile 2.0 inventory file
FACE Profile v 2.0 .svg files
FACE Profile v2.0 RFC cover letter
FACE_Profile_v2.0.xml
Flow-measures for iterative and continuous Software Environments RFC
Flow Measures for Iterative and Continuous Software Environments RFC
Flow Measures for Iterative and Continuous Software Environments RFC INVENTORY
Flow Measures for Iterative and Continuous Software Environments RFC with change bars
Responses for reviewer comments on admtf/2023-08-04
Updated Inventory for Flow Measures for Iterative and Continuous Software Environments RFC
Pending Requests for Information:
All OMG work in progress deadlines in chronological order
Product Knowledge Framework (PKF) RFI
Pending Requests for Proposals:
All OMG work in progress deadlines in chronological order
Agent Metamodel and Profile (AMP) RFP
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.
DDS C# API Request For Proposal
The Data Distribution Service (DDS) specification consists of a UML Platform-Independent Model (PIM) and a single IDL Platform-Specific Model (PSM). As a result, DDS implementations have traditionally implemented APIs that derive directly from the IDL PSM using the standard IDL to language transformations that are available for multiple programming languages. However, often times these IDL-derived mappings preclude programmers from using native programming language constructs, such as generics, that are unavailable in IDL. The result is a suboptimal API that does not conform to the stylistic idioms of the target language, introducing a barrier to the adoption and use of DDS. Since 2012, the OMG has released DDS PSMs that derive directly from the DDS UML PIM, targeting languages like C++ and Java. These new PSMs leverage and conform to the standard data types and programming idioms of such programming languages, simplifying the adoption and use of DDS. Following that evolution, this RFP solicits proposals for a DDS PSM for the C# programming language
DDS Status Monitoring RFP
The Data-Distribution Service (DDS) provides a crucial connectivity platform to many mission critical systems. It is important to have a standardized means for monitoring the health status of the DDS platform during live operation and to use means that are robust to failures of the platform being monitored. This standard covers the information model and technical interfaces required. This RFP solicits proposals for the following: A data model defining the information required for the operational status monitoring of a DDS platform. Techniques, procedures, and interfaces to communicate the data model representing the status of the platform.
Digital Receipt API v1.0 RFP
This RFP solicits proposals for a simplified digital receipt API in which retailers can enable the following: * API specifications that support sharing complete digital receipt data in a secure manner between various parties such as retailers, consumers, product manufacturers, and service providers. * Streamlined standard which specifies a common core of elements to be used in a digital receipt API, which can then be enriched and extended in a standard fashion with local requirements. * Provide the information and evaluation items list that indicates the actual use cases and digital receipt data.
Digital Receipt JSON Document RFP
This RFP solicits proposal for standard Digital Receipt document in JavaScript Object Notation (JSON) [JSON] format. In the past the Association for Retail Technology Standards (ARTS) released a few versions of the Digital Receipt standard XML schemas. The last version of the Digital Receipt 3.1.0 [DR-31] was released in 2017. The changes implemented in that schema were designed to accommodate the requirement of the Japanese market, so that the schema could be used to simplify the processing of POS transactions during the Olympics. Since version 2, the Digital Receipt XML schemas were based on a much larger and more complex POSLog XML schema [POSLOG]. However, in recent years, the shift from using XML format to JSON, especially in messaging and APIs, began to expose limitations of the current Digital Receipt XML standard. Furthermore, the ARTS Digital Receipt specification was primarily focused on the consumer facing aspects of receipt, as a document issued by a retailer to a customer confirming the details of a retail transaction. There is another important aspect of the transactional data. It is used by government agencies for fiscal audit and control of retail operations. Such fiscal receipts include other types of transactions such as tender control or financial transactions performed at a Point of Service (POS). For example, fiscal printers used the same transactional data to print customer receipts as well as to capture fiscal data for government reporting. This RFP solicits proposals for a standard Digital Receipt JSON document that can be used to produce both a consumer facing receipt as well as transactional data for governmental reporting. This RFP solicits proposals for the following: A structure of Digital Receipt JSON document expressed as JSON schema [JSON-S] or Open API Specification [OAS] Schema Objects using YAML syntax. A Retail Industry Ontology that covers the major concepts in the Digital Receipt JSON document.
Enterprise Resource Metadata Attributions (ERMA) Request For Proposal
This RFP focuses on the data requirements for defining a computing environment through the use of Enterprise Resource Metadata Attributions (ERMAs). ERMAs describe the information and data elements needed to provide risk-managed operations within any computing environment. A computing environment comprises, at a minimum: + Hardware: components and relationships (component tree). + Software: systems, applications and services operating on hardware components. + Network Interfaces: the physical communication between components. Optionally, the operational environment may use ERMAs to describe users and data in the operational environment. This RFP explicitly seeks the definitions, structure and vocabularies for the hardware, software and network ERMAs needed to operate a risk-managed computing environment. Optionally, this RFP seeks ERMAs for user and data elements in the computing environment.
Event Metamodel and Profile (EMP) RFP
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.
Ground Data Delivery Interface (GDDI) Request For Proposal
Space vehicle operations require varying compositions of ground applications that are integrated together within a common network (WAN and/or LAN) to provide an end-to-end ground system capability. This includes real time data and metadata transfer across these applications. Typical data includes spacecraft bus commands, telemetry, and mission payload in digital/baseband form. Metadata is carried in-band with the data and includes parameterized information and real-time status used by the ground applications to properly process, store, retrieve, and deliver the data. No common model for this dynamic data/metadata interface currently exists. Approaches, designs, and custom protocols vary widely from one vendor to another offering little opportunity for reuse to system integrators. The result is often a costly and time-consuming integration effort. This RFP solicits proposals for the following: * A Platform-Independent Model describing a lightweight application-level message interface that encapsulates spacecraft data and metadata so they can be transferred between ground applications within a common network. * At least one Platform-Specific Model describing the encoding format of the metadata and data encapsulated by this interface. This platform specific model will call out at least one standard transport layer for carrying the encapsulated/encoded metadata and data, with the intent of reusing an existing transport that provides high throughput, low latency, and optionally secure transmission.
Interface Definition Language v4 (IDL4) to Python Language Mapping RFP
Version 4 of the Interface Definition Language (IDL) specification extends the traditional IDL syntax and defines a comprehensive set of building blocks to categorize it. Such evolution of IDL requires the definition of a new set of language mappings, because existing mappings, such as IDL to Python, do not include complete coverage of the new constructs introduced in IDL version 4 and newer, and do not map well to the new building-block structure. This RFP solicits proposals for an IDL4 to Python mapping
Information Management Metamodel (IMM) RFP
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
RTPS TCP/IP PSM for DDS Interop RFP
The DDS Real-time Publish-Subscribe wire protocol (DDSI-RTPS) specification uses a Model-Driven Architecture (MDA) to describe a Platform Independent Model (PIM) of the interoperability wire protocol and its Platform Specific Mapping (PSM) to the User Datagram Protocol (UDP). The existing standard specifies only a UDP mapping of the PIM that allows conforming implementations to interoperate over UDP. The objective of this RFP is to define a standard PSM to the Transmission Control Protocol (TCP), so that implementations conforming to this specification can interoperate over TCP. Responses to this proposal shall not modify or deprecate UDP-based interoperability or the RTPS PIM.
Robotic Interaction Service Framework 2.0 RFP
This RFP solicits proposals for the following as well as RoIS 1.2 Specification: -Common interfaces between robotic service applications and components that provide functions for performing human-robot interaction. -Data structure for each interface. This RFP also solicits proposals for the following extension to RoIS 1.2 specification: -Semantic definition of requirements and functions of each component using Robotic Service Ontology (RoSO). -Isolation of communication model (infrastructure) of robotic functional components.
Robotic Service Ontology RFP
A service robot is a robot that provides services to humans, or on their behalf, in the environment in which they live or work; by "service", we mean physical services as well as information services that operate in or interoperate with their surroundings, and that are primarily designed to support interaction with people. Service robots are typically designed for consumer rather than commercial purposes. They operate semi- or fully autonomously to perform the services they are designed to deliver, and are capable of decision making and acting in real and unpredictable environments to accomplish specific objectives. To describe the kind of services, capabilities and tasks that such robots might perform, including the terminology used to support rich interfaces between these services, components, sensors, and other elements in the robot's environment, common vocabularies or ontologies defining the robotic services, the related behaviors, the underlying components, and their interfaces are needed. The service robot industry is expected to grow substantially in the coming decades. However, there is no common understanding of the services that might be provided by these robots. We need a common vocabulary or ontology in order to describe robotic services and the components that comprise those services. Such an ontology will assist not only in communications among robots and between robots and the humans they support but will enable developers of both robotic services and robotic functional components to compose higher order robotic services from well-defined, consistent building blocks (components) and have confidence that the resulting services are consistent will work together as designed. IEEE [IEEE1872] provides an ontology that focuses on core (generic) terminology and capability of robot systems at a relatively high level. This ontology includes some basic concepts and definitions that can be revised and extended to meet some of the emerging requirements identified by the robotics community, but does not address requirements specific to robotic services, particularly for service robots (i.e., robots that are designed to interact with people), or meet the requirements specified herein. This RFP solicits proposals for the following: o A set of basic ontologies that provide a semantic model of robotic services and related robotic functional components that can support communications and interoperability between robotic services and enable composition of such services
Semantic Information Modeling for Federation (SIMF) RFP
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.
SBRM RFP
This RFP solicits a specification that complements established mechanisms for representation of structured data files submitted as business reports, typically financial reports to regulators, in formats such as XBRL, by - Applying a business modeling approach to report definition, making reports easier to develop; - Enabling business-level expression of rules in order to manage quality; - Facilitating reuse of information across multiple reports; - Allowing use with industry- or enterprise-standard information models and ontologies; - Allowing direct linkage with enterprise information sources for report data; - Providing alternative formats for reports to allow access by a greater variety of analytical tooling while providing interoperability with XBRL-based report definitions and report submissions.
UnifiedPOS Fiscal API 2.0 RFP
This RFP solicits proposals for the following: A platform independent behavioral model to describe interactions between fiscal devices or services and applications that consume them. A standard Fiscal API to register retail transactions on a fiscal device or tax authority service. A standard Fiscal API to store data into a fiscal journal
UnifiedPOS V2 Model And POS Printer API RFP
This RFP solicits proposals for the following: A platform independent behavioural model to describe interactions between device services and applications that consume them. The new model should address the shortcomings of the UnifiedPOS V1 and provide a foundation for exposing devices as services. An API to query POS printer capabilities. An API to print information on paper rolls using receipt and journal stations of the POS printer. An API to print information on a form (typically a check or credit card slip) on the slip station of the POS printer.
Current Specification Revision Processes (available to members only):
APIs for Knowledge Platforms 1.1 RTFAction Language for fUML 1.2 (ALF) RTF
Alert Management Service (ALMAS) 1.4 RTF
Automated Technical Debt Measure V2 1.0 FTF
BMM 1.4 RTF
BPM+ Knowledge Package Model and Notation (BKPMN) 1.0 FTF
Business Architecture Core Metamodel (BACM) 1.1 RTF
CORBA 3.5 RTF
Command and Control Interface for Navigation Systems (C2INav) 1.3 RTF
Command and Control Message Specification (C2MS) 1.1 RTF
Commons Ontology Library (Commons) 1.1 RTF
Commons Ontology Library (Commons) 1.2 RTF
CubeSat System Reference Model Profile (CSRM) 1.1 RTF
DDS Consolidated JSON Syntax (DDS-JSON) 1.1 RTF
DDS Consolidated XML Syntax (DDS-XML) 1.1 RTF
DDS Extensible Types (DDS-XTYPES) 1.4 RTF
DDS Extensions for Time Sensitive Networking (DDS-TSN) 1.0 FTF
DDS Security 1.2 RTF
DDS-OPC UA Gateway 1.1 RTF
DDS-PSM-Cxx v1.1 RTF
DDS-PSM-JAVA 1.1 RTF
DDS-XRCE 1.1 RTF
DOL 1.1 RTF
Decision Model and Notation 1.6 RTF
Diagram Definition 1.2 RTF
Digital Receipt API Specification 1.0 FTF
Essence 1.3 RTF
FACE Profile (FACE) 2.0 FTF
FIGI 1.1 RTF
GEMS 1.6 RTF
IDL to C++11 1.7 RTF
IDL4 to C# Language Mapping (IDL4-CSHARP) 1.1 RTF
IDL4 to C++ Language Mapping (IDL4-CPP) 1.0 FTF
IDL4 to Java Language Mapping (IDL4-Java) 1.1 RTF
Interface Definition Language 4.3 RTF
Kernel Modeling Language (KerML) 1.0 FTF
Languages, Countries and Codes 1.3 RTF
MARTE 1.4 RTF
MOF 2.6 RTF
MOF to RDF Mapping 1.1 RTF
Multiple Vocabulary Facility (MVF) 1.1 RTF
Object Constraint Language 2.5 RTF
Ontology Definition Metamodel (ODM) 1.2 RTF
Open Architecture Radar Interface Standard (OARIS) 2.1 RTF
Open Architecture Radar Interface Standard (OARIS) 3.0 FTF
PSSM 1.1 RTF
Pedigree and Provenance Model and Notation (PPMN) FTF 2
Precise Semantics for Uncertainty Modeling (PSUM) 1.0 FTF
QVT 1.4 RTF
RPC over DDS 1.1 RTF
Requirements Interchange Format V1.3 (ReqIF) RTF
Risk Analysis and Assessment Modeling Language (RAAML) 1.1 RTF
Robotic Service Ontology (RoSo) 1.0 FTF
SACM 2.4 RTF
SBVR 1.6 RTF
SOLM 1.1 RTF
Situational Data Model and Notation (SDMN) 1.0 FTF
Software Fault Pattern Metamodel (SFPM) 1.1 RTF
Space Telecommunications Interface (STI) 1.1 RTF
Specification Common Elements (SCE) 1.0 FTF 2
SysPhS 1.2 RTF
Systems Modeling API and Services (SystemsModelingAPI) 1.0 FTF
Systems Modeling Language (SysML) 2.0 FTF
TACSIT Controller Interface (TCI) 1.1 RTF
TACSIT Data Exchange (TEX) 1.1 RTF
TACSIT Data Exchange (TEX) 1.2 RTF
TOIF 1.4 RTF
Tactical Decision Aids Interface (TDAI) 1.0 FTF2
UCM 1.4 RTF
UML 2.6 RTF
UML Profile for ROSETTA (UPR) 1.1 RTF
UML Testing Profile 2 (UTP2) 2.2 RTF
UML Testing Profile 2 (UTP2) 2.3 RTF
Unified Architecture Framework (UAF) 1.3 RTF
UnifiedPOS 1.15.1 RTF
UnifiedPOS 1.16.2 RTF
VDML 1.2 RTF
XMI 2.6 RTF
XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF
XTCE US Government Satellite Conformance Profile 1.1 RTF