public:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-2-complementarity-with-exchange-and-semantic-federation-specifications: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-2-complementarity-with-exchange-and-semantic-federation-specifications: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-2-complementarity-with-exchange-and-semantic-federation-specifications:start to public:00-sip-ra:06-specific-requirements-on-proposal nick_didopublic:00-sip-ra:06-specific-requirements-on-proposals:06-3-relationship-to-other-omg-specifications:06-3-2-complementarity-with-exchange-and-semantic-federation-specifications:start [2026/09/14 17:49] (current) – nick_dido
Line 1: Line 1:
 ====== 6.3.2 Complementarity with Exchange and Semantic Federation Specifications ====== ====== 6.3.2 Complementarity with Exchange and Semantic Federation Specifications ======
  
-[[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 complement existing OMG specifications that address interoperability and semantic federation, without duplicating their scope.+The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] complements existing OMG specifications addressing information exchange, [[public:99_annexes:annex-b-terms-and-definitions:i:interoperability|Interoperability]], [[public:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]], and [[public:99_annexes:annex-b-terms-and-definitions:f:federation|Federation]]. It provides Governance and structural abstractions without duplicating the established scope or capabilities of those specifications.
  
-  - Proposals SHALL describe how the submitted architecture complements existing OMG specifications addressing information exchange and interoperability. +===== Requirements ===== 
-  - Proposals SHALL describe how the submitted architecture relates to OMG specifications addressing semantic federation and ontology-based modeling. + 
-  - Proposals SHALL identify architectural integration points with exchange and semantic federation frameworks while preserving independence from any specific transport, exchange, or modeling standard. +^ Requirement ^ Statement ^ 
-  - Proposals SHALL NOT redefine or replicate capabilities already standardized within existing OMG exchange, interoperability, or semantic federation specifications.+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-035-complementarity-with-exchange-and-interoperability-specifications|SIP-035 — Complementarity with Exchange and Interoperability Specifications]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-035-complementarity-with-exchange-and-interoperability-specifications#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-036-relationship-to-semantic-federation-and-ontology-modeling|SIP-036 — Relationship to Semantic Federation and Ontology Modeling]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-036-relationship-to-semantic-federation-and-ontology-modeling#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-037-technology-neutral-integration-points|SIP-037 — Technology-Neutral Integration Points]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-037-technology-neutral-integration-points#Statement&noheader&nofooter&noeditbtn}} | 
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-038-nonduplication-of-existing-capabilities|SIP-038 — Nonduplication of Existing Capabilities]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-038-nonduplication-of-existing-capabilities#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 prohibits replacing, superseding, or modifying existing OMG specifications. SIP-038 prohibits redefining or duplicating capabilities already standardized within the established scope of those specifications. 
 + 
 +SIP-034 applies specifically to existing transport, information-exchange, message-exchange, and message-layer constructs. SIP-038 extends the nonduplication principle to Interoperability and semantic-Federation capabilities.
  
 ---- ----
Line 15: Line 30:
 © 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-2-complementarity-with-exchange-and-semantic-federation-specifications/start.1789263206.txt.gz
  • Last modified: 2026/09/12 18:33
  • by nick_dido