| Both sides previous revision Previous revision Next revision | Previous revision |
| public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-3-modeling-neutrality:start [2026/09/12 18:34] – ↷ Links adapted because of a move operation nick_dido | public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-3-modeling-neutrality:start [2026/09/14 18:06] (current) – nick_dido |
|---|
| [[public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:start|Return to Relationship to Other OMG Specifications]] | [[public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:start|Return to Relationship to Other OMG Specifications]] |
| |
| The submitted architecture is expected to remain platform-independent and modeling-language neutral. | The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] remains platform-independent and independent of any particular modeling syntax, diagrammatic notation, model-interchange format, or vendor tooling environment. |
| |
| - Proposals SHALL define the [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] at a platform-independent level without requiring the use of any specific modeling language or notation. | 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 [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]]. |
| - Proposals SHALL ensure that the architectural constructs, roles, relationships, and governance mechanisms are defined independently of any particular modeling syntax or diagrammatic representation. | |
| - Proposals SHALL NOT require the use of any specific modeling language, interchange format, or vendor tooling environment as a condition of conformance. | ===== Requirements ===== |
| | |
| | ^ Requirement ^ Statement ^ |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-039-platform-independent-modeling|SIP-039 — Platform-Independent Modeling]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-039-platform-independent-modeling#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-040-representation-independent-architectural-constructs|SIP-040 — Representation-Independent Architectural Constructs]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-040-representation-independent-architectural-constructs#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-041-modeling-and-tooling-conformance-neutrality|SIP-041 — Modeling and Tooling Conformance Neutrality]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-041-modeling-and-tooling-conformance-neutrality#Statement&noheader&nofooter&noeditbtn}} | |
| | |
| | ===== 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. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| </WRAP> | </WRAP> |
| |