| Both sides previous revision Previous revision Next revision | Previous revision |
| public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-1-in-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-1-in-scope:start [2026/09/14 17:06] (current) – nick_dido |
|---|
| [[public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]] | [[public:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]] |
| |
| The following requirements define the architectural capabilities and abstractions that proposals SHALL address. | The following requirements define the architectural capabilities and abstractions that a Submission SHALL address. Unless otherwise stated, each requirement applies to the Submission and the proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] described by that Submission. |
| |
| - Proposals SHALL define a platform-independent [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] and its formal [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]]. | ===== Requirements ===== |
| - Proposals SHALL define the architectural elements, roles, relationships, and interaction constructs that comprise the Reference Architecture. | |
| - Proposals SHALL distinguish data, [[public:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], semantics, and interpretation as separable but coordinated architectural concerns. | ^ Requirement ^ Statement ^ |
| - Proposals SHALL define an architectural construct representing the flow of structured information between architectural elements. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-001-platform-independent-reference-architecture|SIP-001 — Platform-Independent Reference Architecture]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-001-platform-independent-reference-architecture#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define ordered processing flows composed of modular components connected through governed interaction constructs. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-002-formal-platform-independent-model|SIP-002 — Formal Platform Independent Model]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-002-formal-platform-independent-model#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define explicit attachment points through which structured information enters and exits architectural elements. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-003-reference-architecture-constituents|SIP-003 — Reference Architecture Constituents]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-003-reference-architecture-constituents#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define boundary constructs governing ingress, transformation, and egress of structured information. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-004-separation-of-architectural-concerns|SIP-004 — Separation of Architectural Concerns]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-004-separation-of-architectural-concerns#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define version-controlled interface contracts governing the exchange of structured information across attachment points. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-005-structured-information-flow|SIP-005 — Structured Information Flow]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-005-structured-information-flow#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define lifecycle governance mechanisms governing structural artifacts. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-006-ordered-modular-processing-flows|SIP-006 — Ordered Modular Processing Flows]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-006-ordered-modular-processing-flows#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define lifecycle governance mechanisms governing semantic artifacts. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-007-structured-information-attachment-points|SIP-007 — Structured Information Attachment Points]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-007-structured-information-attachment-points#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define lifecycle governance mechanisms governing interpretive artifacts. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-008-information-boundary-constructs|SIP-008 — Information Boundary Constructs]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-008-information-boundary-constructs#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms supporting reproducible interpretation under version-controlled conditions. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-009-version-controlled-interface-contracts|SIP-009 — Version-Controlled Interface Contracts]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-009-version-controlled-interface-contracts#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms by which jurisdictions retain control over structural definitions within their operational boundary. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-010-structural-artifact-lifecycle-governance|SIP-010 — Structural Artifact Lifecycle Governance]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-010-structural-artifact-lifecycle-governance#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms by which jurisdictions retain control over semantic definitions within their operational boundary. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-011-semantic-artifact-lifecycle-governance|SIP-011 — Semantic Artifact Lifecycle Governance]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-011-semantic-artifact-lifecycle-governance#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define modular integration constructs that support operations across jurisdictional boundaries. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-012-interpretive-artifact-lifecycle-governance|SIP-012 — Interpretive Artifact Lifecycle Governance]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-012-interpretive-artifact-lifecycle-governance#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define modular integration constructs supporting operation across security boundaries. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-013-reproducible-interpretation|SIP-013 — Reproducible Interpretation]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-013-reproducible-interpretation#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms enforcing segmentation of information flows based on governance or security constraints. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-014-jurisdictional-control-of-structural-definitions|SIP-014 — Jurisdictional Control of Structural Definitions]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-014-jurisdictional-control-of-structural-definitions#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms separating the data plane and control plane. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-015-jurisdictional-control-of-semantic-definitions|SIP-015 — Jurisdictional Control of Semantic Definitions]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-015-jurisdictional-control-of-semantic-definitions#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL distinguish governance constraints from interface contracts. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-016-cross-jurisdictional-integration|SIP-016 — Cross-Jurisdictional Integration]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-016-cross-jurisdictional-integration#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define conformance requirements independently of interface interaction definitions. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-017-cross-security-boundary-integration|SIP-017 — Cross-Security-Boundary Integration]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-017-cross-security-boundary-integration#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define conformance points supporting inspection and verification independent of implementation technology. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-018-information-flow-segmentation|SIP-018 — Information-Flow Segmentation]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-018-information-flow-segmentation#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL define architectural mechanisms that separate governance artifact evolution from the execution of the operational processing flow. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-019-data-plane-and-control-plane-separation|SIP-019 — Data Plane and Control Plane Separation]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-019-data-plane-and-control-plane-separation#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-020-governance-constraints-and-interface-contracts|SIP-020 — Governance Constraints and Interface Contracts]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-020-governance-constraints-and-interface-contracts#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-021-independent-conformance-requirements|SIP-021 — Independent Conformance Requirements]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-021-independent-conformance-requirements#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-022-technology-independent-conformance-points|SIP-022 — Technology-Independent Conformance Points]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-022-technology-independent-conformance-points#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-023-governance-evolution-and-operational-execution|SIP-023 — Governance Evolution and Operational Execution]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-023-governance-evolution-and-operational-execution#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. |
| |
| ---- | ---- |
| © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| </WRAP> | </WRAP> |
| |