| 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/14 17:51] – 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 |
|---|
| 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. | 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. |
| |
| Modeling neutrality applies to implementations claiming conformance to the Reference Architecture. It does not prevent the adopted specification from using an OMG modeling language or notation to express its normative [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]]. | 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)]]. |
| |
| ===== Requirements ===== | ===== Requirements ===== |
| |
| * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-001-platform-independent-reference-architecture|SIP-001 — Platform-Independent Reference Architecture]]:** The proposed Reference Architecture SHALL be platform independent | ^ 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}} | |
| |
| * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-039-modeling-language-and-notation-neutrality|SIP-039 — Modeling-Language and Notation Neutrality]]:** The architectural model SHALL define its constructs, roles, relationships, and Governance mechanisms independently of any particular modeling syntax or diagrammatic notation | ===== Notes for Editors ===== |
| |
| * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-040-model-interchange-format-neutrality|SIP-040 — Model-Interchange-Format Neutrality]]:** The conformance requirements SHALL NOT require implementations to use a specific model-interchange format | The requirement identifiers and short titles link to the authoritative requirement records in Annex C. |
| |
| * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-030-tool-and-technology-neutrality|SIP-030 — Tool and Technology Neutrality]]:** The conformance requirements SHALL NOT require a specific modeling language, transport framework, or vendor tooling environment | The Statements displayed in this section are transcluded from the corresponding Annex C requirement pages and are not independently maintained copies. |
| | |
| ===== Notes for Editors ===== | |
| |
| SIP-001 and SIP-030 are reused here because Annex C already governs platform independence and tool neutrality. | Make changes to a Statement on its Annex C requirement page. |
| |
| SIP-039 addresses independence from the syntax or diagrammatic notation used to represent architectural concepts. SIP-040 addresses independence from a particular model-interchange format. | SIP-001 establishes the general platform independence of the proposed Reference Architecture. SIP-039 applies that principle specifically to its architectural modeling. |
| |
| SIP-002 requires the Submission to include a formal PIM. The adopted specification may use an OMG modeling language and a standardized interchange format to express and distribute that normative model. SIP-030, SIP-039, and SIP-040 prevent those specification-authoring choices from becoming required implementation technologies or tools. | 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. |
| |
| After SIP-039 and SIP-040 are created and reviewed in Annex C, replace the locally maintained Statements in this section with transclusions of their authoritative Statements. | 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. |
| |
| ---- | ---- |