Table of Contents

6.3.1 Architectural Positioning

Return to Relationship to Other OMG Specifications

The proposed Reference Architecture occupies an architectural layer concerned with Governance and structural abstractions. This positioning distinguishes its responsibilities from transport, information exchange, message exchange, and Federation mechanisms addressed by existing OMG specifications.

Requirements

Requirement Statement
SIP-031 — Architectural Positioning

The proposed Reference Architecture SHALL be positioned at the architectural Governance and structural abstraction layer.

SIP-032 — Separation from Existing Mechanisms

The architectural model SHALL distinguish Governance constructs from transport, information-exchange, message-exchange, and Federation mechanisms defined by existing OMG specifications.

SIP-033 — Architectural Layering

The architectural model SHALL define layering that separates structural and Governance concerns from transport, information-exchange, message-exchange, and Federation mechanisms.

SIP-034 — Preservation of Existing Transport and Exchange Constructs

The proposed Reference Architecture SHALL NOT redefine, duplicate, or supersede transport, information-exchange, message-exchange, or message-layer constructs defined by existing OMG specifications.

Notes for Editors

The requirement identifiers and short titles link to the authoritative requirement records in Annex C.

The Statements displayed in this section are transcluded from the corresponding Annex C requirement pages and are not independently maintained copies.

Make changes to a Statement on its Annex C requirement page.

SIP-026 applies broadly to existing OMG specifications addressing information exchange, interoperability, or semantic Federation. SIP-034 applies specifically to the transport, information-exchange, message-exchange, and message-layer constructs preserved by the architectural positioning defined in this section.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.