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/12 18:34] – ↷ Links adapted because of a move operation 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 3: / Line 3: @@
 [[public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]]
-The requested [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] is limited to architectural abstraction and governance constructs.
+The following requirements identify matters that SHALL remain outside the scope of the proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. Unless otherwise stated, each requirement applies to the Submission and the proposed Reference Architecture described by that Submission.
-The following exclusions clarify the boundaries of the requested Reference Architecture and prevent overlap with existing OMG specifications, domain standards, and implementation technologies.
+===== Requirements =====
-  - Proposals SHALL NOT define domain-specific data content or operational data models.
+^ Requirement ^ Statement ^
-  - Proposals SHALL NOT define transport protocols, message exchange frameworks, or runtime communication mechanisms.
+| [[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}} |
-  - Proposals SHALL NOT replace, supersede, or modify existing OMG specifications addressing exchange, interoperability, or semantic federation.
+| [[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}} |
-  - Proposals SHALL NOT standardize any specific ontology, vocabulary, or domain taxonomy.
+| [[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}} |
-  - Proposals SHALL NOT define operational doctrine, mission procedures, or domain policy rules.
+| [[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}} |
-  - Proposals SHALL NOT prescribe specific implementation technologies, deployment topologies, or system architectures.
+| [[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}} |
-  - Proposals SHALL NOT require the use of any specific modeling language, transport framework, or vendor tooling environment.
+| [[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}} |
+===== 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.
+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.
 ----