Return to Scope of Proposals Sought
The following requirements identify matters that SHALL remain outside the scope of the proposed Reference Architecture. Unless otherwise stated, each requirement applies to the Submission and the proposed Reference Architecture described by that Submission.
| Requirement | Statement |
|---|---|
| SIP-024 — Domain-Specific Content Exclusion |
The proposed Reference Architecture SHALL NOT define Domain-specific Data content or operational Data Models. |
| SIP-025 — Transport and Runtime Mechanism Exclusion |
The proposed Reference Architecture SHALL NOT define transport protocols, message-exchange frameworks, or runtime communication mechanisms. |
| 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. |
| SIP-027 — Ontology, Vocabulary, and Taxonomy Exclusion |
The proposed Reference Architecture SHALL NOT standardize a specific Ontology, Vocabulary, or Domain Taxonomy. |
| SIP-028 — Doctrine, Procedure, and Policy Exclusion |
The proposed Reference Architecture SHALL NOT define operational doctrine, mission procedures, or Domain Policy rules. |
| SIP-029 — Implementation and Deployment Independence |
The proposed Reference Architecture SHALL NOT prescribe specific implementation technologies, deployment topologies, or System architectures. |
| SIP-030 — Tool and Technology Neutrality |
The conformance requirements SHALL NOT require a specific modeling language, transport framework, or vendor tooling environment. |
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.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.