Differences

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

--- public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-3-data-structure-semantics-and-interpretation: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-4-required-submission-content:06-4-3-data-structure-semantics-and-interpretation:start [2026/09/14 18:42] (current) – nick_dido
@@ Line 3: / Line 3: @@
 [[public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]]
-The [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] SHALL define architectural separation and lifecycle governance of data, [[public:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], semantics, and interpretation.
+The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] separates and coordinates [[public:99_annexes:annex-b-terms-and-definitions:d:data|Data]], [[public:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]], [[public:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]], and [[public:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]]. It also governs the definition, versioning, lifecycle, and application of structural, semantic, and interpretive [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] independently of particular implementation systems.
-  - Proposals SHALL describe how data, structure, semantics, and interpretation are defined as distinct but coordinated architectural concerns.
+===== Requirements =====
-  - Proposals SHALL describe how structural artifacts are formally defined, versioned, and governed independently of implementation systems.
-  - Proposals SHALL describe how semantic artifacts are formally defined, versioned, and governed independently of implementation systems.
+^ Requirement ^ Statement ^
-  - Proposals SHALL describe how interpretive logic is formally defined, versioned, and governed independently of structural and semantic artifacts.
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-049-architectural-concern-and-lifecycle-description|SIP-049 — Architectural Concern and Lifecycle Description]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-049-architectural-concern-and-lifecycle-description#Statement&noheader&nofooter&noeditbtn}} |
-  - Proposals SHALL define architectural mechanisms that separate interpretive logic from implementation environments.
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-050-implementation-independent-interpretive-logic|SIP-050 — Implementation-Independent Interpretive Logic]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-050-implementation-independent-interpretive-logic#Statement&noheader&nofooter&noeditbtn}} |
-  - Proposals SHALL define architectural mechanisms that ensure interpretive outcomes are reproducible solely from explicitly versioned structural, semantic, and interpretive artifacts.
+===== Required Coverage =====
+The description required by SIP-049 includes the architectural information governed by the following requirements:
+^ Requirement ^ Required Architectural Information ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-004-separation-of-architectural-concerns|SIP-004 — Separation of Architectural Concerns]] | Data, Structure, Semantics, and Interpretation as separable but coordinated architectural concerns |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-010-structural-artifact-lifecycle-governance|SIP-010 — Structural Artifact Lifecycle Governance]] | Lifecycle controls for structural Artifacts |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-011-semantic-artifact-lifecycle-governance|SIP-011 — Semantic Artifact Lifecycle Governance]] | Lifecycle controls for semantic Artifacts |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-012-interpretive-artifact-lifecycle-governance|SIP-012 — Interpretive Artifact Lifecycle Governance]] | Lifecycle controls for interpretive Artifacts |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-013-reproducible-interpretation|SIP-013 — Reproducible Interpretation]] | Reproduction of an Interpretation using identified, version-controlled conditions |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-023-governance-evolution-and-operational-execution|SIP-023 — Governance Evolution and Operational Execution]] | Separation of Governance Artifact evolution from execution of the operational processing flow |
+===== Notes for Editors =====
+The links to SIP-049 and SIP-050 provide temporary access to their individual Annex C requirement pages while those records are being created and reviewed.
+After those records are complete, replace each locally maintained Statement with a transclusion of its authoritative Statement.
+SIP-049 governs the required description. The requirements listed under Required Coverage govern the underlying architectural capabilities and constraints.
+SIP-010 through SIP-012 govern the lifecycles of structural, semantic, and interpretive Artifacts. Their detailed requirement records should address formal definition, identification, versioning, authority, status, applicability, and change control.
+SIP-013 already requires reproducible Interpretation under identified, version-controlled conditions. It is not repeated or renumbered in this section.
+SIP-050 adds the distinct requirement that interpretive logic remain architecturally separate from the implementation environments that execute or otherwise apply it.
+The Required Coverage table provides a nonnormative summary. The corresponding Annex C requirement records remain authoritative.
 ----
@@ Line 17: / Line 44: @@
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP>