public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-1-architectural-positioning:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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-1-architectural-positioning:start [2026/09/12 18:33] – ↷ Page moved from dido:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-1-architectural-positioning:start to public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specificat nick_didopublic:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-1-architectural-positioning:start [2026/09/14 17:42] (current) – nick_dido
Line 1: Line 1:
 ====== 6.3.1 Architectural Positioning ====== ====== 6.3.1 Architectural Positioning ======
  
-[[dido: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 define governance and structural abstractions distinct from transport, exchange, and federation mechanisms addressed by existing OMG specifications.+The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] occupies an architectural layer concerned with [[public:99_annexes:annex-b-terms-and-definitions:g:governance|Governance]] and structural abstractions. This positioning distinguishes its responsibilities from transport, information exchange, message exchange, and [[public:99_annexes:annex-b-terms-and-definitions:f:federation|Federation]] mechanisms addressed by existing OMG specifications.
  
-  - Proposals SHALL position the submitted architecture at the architectural governance and structural abstraction layer. +===== Requirements ===== 
-  - Proposals SHALL distinguish governance constructs from transport, exchange, and federation mechanisms defined in existing OMG specifications. + 
-  - Proposals SHALL define architectural layering that separates structural and governance concerns from transport, exchange, and federation mechanisms. +^ Requirement ^ Statement ^ 
-  - Proposals SHALL NOT redefine, duplicate, or supersede transport, exchange, or message-layer constructs defined by existing OMG specifications.+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-031-architectural-positioning|SIP-031 — Architectural Positioning]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-031-architectural-positioning#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-032-separation-from-existing-mechanisms|SIP-032 — Separation from Existing Mechanisms]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-032-separation-from-existing-mechanisms#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-033-architectural-layering|SIP-033 — Architectural Layering]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-033-architectural-layering#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-034-preservation-of-existing-transport-and-exchange-constructs|SIP-034 — Preservation of Existing Transport and Exchange Constructs]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-034-preservation-of-existing-transport-and-exchange-constructs#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-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.
  
 ---- ----
Line 15: Line 28:
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP> </WRAP>
- 
  • public/00-sip-ra/06-specific-requirements-on-proposals/06-3-relationship-to-other-omg-specifications/06-3-1-architectural-positioning/start.1789263205.txt.gz
  • Last modified: 2026/09/12 18:33
  • by nick_dido