6.3.3 Modeling Neutrality
Return to Relationship to Other OMG Specifications
The proposed Reference Architecture remains platform-independent and independent of any particular modeling syntax, diagrammatic notation, model-interchange format, or vendor tooling environment.
Modeling neutrality applies to implementations claiming conformance to the Reference Architecture. It does not prevent the adopted specification from using an OMG modeling language, notation, or interchange format to express and distribute its normative Platform Independent Model (PIM).
Requirements
| Requirement | Statement |
|---|---|
| SIP-039 — Platform-Independent Modeling |
The proposed Reference Architecture SHALL be defined at a platform-independent level without requiring a specific modeling language or notation. |
| SIP-040 — Representation-Independent Architectural Constructs |
The architectural model SHALL define its constructs, roles, relationships, and Governance mechanisms independently of any particular modeling syntax or diagrammatic representation. |
| SIP-041 — Modeling and Tooling Conformance Neutrality |
The conformance requirements SHALL NOT require implementations to use a specific modeling language, model-interchange format, or vendor tooling environment. |
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-001 establishes the general platform independence of the proposed Reference Architecture. SIP-039 applies that principle specifically to its architectural modeling.
SIP-030 establishes general tool and technology neutrality. SIP-041 applies that principle specifically to modeling languages, model-interchange formats, and modeling tools used by conforming implementations.
SIP-002 requires the Submission to include a formal PIM. The adopted specification may select an OMG modeling language and a standardized interchange format to express and distribute that normative model. Such specification-authoring choices do not become required implementation technologies or tools.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.