Differences

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

--- public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-2-out-of-scope:start [2026/09/14 17:14] – nick_dido
+++ public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-2-out-of-scope:start [2026/09/14 17:30] (current) – nick_dido
@@ Line 7: / Line 7: @@
 ===== Requirements =====
-  * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-024-domain-specific-content-exclusion|SIP-024 — Domain-Specific Content Exclusion]]:** The proposed Reference Architecture SHALL NOT define Domain-specific Data content or operational Data Models
+^ Requirement ^ Statement ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-024-domain-specific-content-exclusion|SIP-024 — Domain-Specific Content Exclusion]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-024-domain-specific-content-exclusion#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-025-transport-and-runtime-mechanism-exclusion|SIP-025 — Transport and Runtime Mechanism Exclusion]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-025-transport-and-runtime-mechanism-exclusion#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-026-preservation-of-existing-omg-specifications|SIP-026 — Preservation of Existing OMG Specifications]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-026-preservation-of-existing-omg-specifications#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-027-ontology-vocabulary-and-taxonomy-exclusion|SIP-027 — Ontology, Vocabulary, and Taxonomy Exclusion]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-027-ontology-vocabulary-and-taxonomy-exclusion#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-028-doctrine-procedure-and-policy-exclusion|SIP-028 — Doctrine, Procedure, and Policy Exclusion]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-028-doctrine-procedure-and-policy-exclusion#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-029-implementation-and-deployment-independence|SIP-029 — Implementation and Deployment Independence]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-029-implementation-and-deployment-independence#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-030-tool-and-technology-neutrality|SIP-030 — Tool and Technology Neutrality]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-030-tool-and-technology-neutrality#Statement&noheader&nofooter&noeditbtn}} |
-  * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-025-transport-and-runtime-mechanism-exclusion|SIP-025 — Transport and Runtime Mechanism Exclusion]]:** The proposed Reference Architecture SHALL NOT define transport protocols, message-exchange frameworks, or runtime communication mechanisms
+===== Notes for Editors =====
-  * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-026-preservation-of-existing-omg-specifications|SIP-026 — Preservation of Existing OMG Specifications]]:** The Submission SHALL NOT replace, supersede, or modify existing OMG specifications addressing information exchange, interoperability, or semantic federation
+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-027-ontology-vocabulary-and-taxonomy-exclusion|SIP-027 — Ontology, Vocabulary, and Taxonomy Exclusion]]:** The proposed Reference Architecture SHALL NOT standardize a specific ontology, Vocabulary, or Domain taxonomy
-  * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-028-doctrine-procedure-and-policy-exclusion|SIP-028 — Doctrine, Procedure, and Policy Exclusion]]:** The proposed Reference Architecture SHALL NOT define operational doctrine, mission procedures, or Domain Policy rules
-  * **[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-029-implementation-and-deployment-independence|SIP-029 — Implementation and Deployment Independence]]:** The proposed Reference Architecture SHALL NOT prescribe specific implementation technologies, deployment topologies, or System architectures
-  * **[[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
-===== Notes for Editors =====
-The links in this section provide temporary access to the individual Annex C requirement pages while those records are being created and reviewed.
+The Statements displayed in this section are transcluded from the corresponding Annex C requirement pages and are not independently maintained copies.
-After the Annex C records are complete, replace each locally maintained Statement with a transclusion of the authoritative Statement from its corresponding requirement page.
+Make changes to a Statement on its Annex C requirement page.
 An exclusion does not prohibit a Submission from referencing an existing specification or providing a nonnormative example. It prevents the proposed Reference Architecture from standardizing content or technology that lies outside the scope of this RFP.