You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h3class="heading settled" data-level="1.1" id="status"><spanclass="secno">1.1. </span><spanclass="content">Status of This Document</span><aclass="self-link" href="#status"></a></h3>
737
-
<p>This document is a <strong>CG Draft</strong> of the RecordWeb Community Group. It is an Editor’s Draft and does not represent a W3C standard or endorsed position.</p>
738
-
<p>The published baseline of this concept is available at <adata-link-type="biblio" href="#biblio-zenodo-rwc" title="RecordWeb Concept (RWC) v1.0 — Published baseline">[ZENODO-RWC]</a> (Version 1.0, DOI: 10.5281/zenodo.20475343). This working document reflects ongoing development toward the Community Group deliverable.</p>
740
+
<p>This document is a <strong>CG Draft</strong> of the RecordWeb Community Group. It is an Editor’s Draft maintained in the group’s repository and does not represent a W3C standard or endorsed position.</p>
741
+
<p>The published baseline of this concept is available at <adata-link-type="biblio" href="#biblio-zenodo-rwc" title="RecordWeb Concept (RWC) v1.0 — Published baseline">[ZENODO-RWC]</a> (DOI: 10.5281/zenodo.20475343). This working document reflects ongoing development toward the Community Group deliverable.</p>
739
742
<p>Feedback is invited via <ahref="https://github.com/recordweb/rwc/issues">GitHub Issues</a>.</p>
<p>Public administrations have managed information for decades in systems built for filing, not for traceability. The result is well known: incomplete dossiers, lost version histories, system boundaries that fragment information, and an institutional memory that promises more than it delivers.</p>
<p>The Records Continuum provides no structural answer to these questions. It describes how Records are <em>meaningful</em>, but not how they are <em>provable</em>. This is not a flaw in the model; it was not designed for this purpose. But it is the gap that RecordWeb must close.</p>
<p>On the other side stands the classical lifecycle, as anchored in <adata-link-type="biblio" href="#biblio-iso15489" title="ISO 15489-1:2016 — Information and documentation — Records management">[ISO15489]</a> and in Switzerland in <adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 — Information lifecycle in public administration">[ECH-0164]</a>: processing — retention — archiving or disposal.</p>
839
+
<p>On the other side stands the classical lifecycle, as anchored in <adata-link-type="biblio" href="#biblio-iso15489" title="ISO 15489-1:2016 — Information and documentation — Records management">[ISO15489]</a> and in Switzerland in <adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 Information lifecycle in public administration (V1.1, in preparation)">[ECH-0164]</a>: processing — retention — archiving or disposal.</p>
837
840
<p>This framework has great merits. It creates clarity about responsibilities, enables legally compliant retention periods, and structures the transition between operational use and historical preservation. But the model carries a structural cost: it thinks in system boundaries. A Record "lives" in one system and is "moved" to another. Every transition is a migration, a transformation, a potential loss of information.</p>
838
841
<h3class="heading settled" data-level="4.4" id="synthesis"><spanclass="secno">4.4. </span><spanclass="content">RecordWeb as Synthesis</span><aclass="self-link" href="#synthesis"></a></h3>
839
842
<p>RecordWeb postulates that the tension between continuity and provability cannot be resolved through a better lifecycle model, but through a different approach.</p>
<p><strong>Usability</strong>: The DID document and <adata-link-type="dfn" href="#metadata" id="ref-for-metadata④">metadata</a> guarantee that a <adata-link-type="dfn" href="#record" id="ref-for-record⑥⑥">Record</a> remains findable and accessible, regardless of system migrations</p>
1053
1056
</ul>
1054
-
<p><adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 — Information lifecycle in public administration">[ECH-0164]</a> defines the information lifecycle for Swiss administration. RecordWeb reinterprets this model: the three phases become states within a single information object, without system boundaries between them.</p>
1057
+
<p><adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 Information lifecycle in public administration (V1.1, in preparation)">[ECH-0164]</a> defines the information lifecycle for Swiss administration. RecordWeb reinterprets this model: the three phases become states within a single information object, without system boundaries between them.</p>
<p>OAIS <adata-link-type="biblio" href="#biblio-iso14721" title="ISO 14721:2012 — Open Archival Information System (OAIS)">[ISO14721]</a> is the international standard for digital long-term preservation. RecordWeb and OAIS are complementary: RecordWeb covers the operational phase; OAIS covers long-term preservation. RecordWeb <adata-link-type="dfn" href="#record" id="ref-for-record⑥⑦">Records</a> can be migrated to long-term archives according to OAIS principles; the DID is retained in this process.</p>
<p>RecordWeb has the potential to contribute to international standardisation processes. This path is long. It begins with the concept, proceeds through the specification, and is validated through implementations.</p>
<p>The following questions are explicitly offered for community contribution:</p>
1142
-
<p><strong>Access control</strong>: RecordWeb deliberately defines no authorisation model. Data security and information protection are delegated to the implementing systems. The specification provides an optional <code>access-policy</code> block in the minimum metadata set.</p>
1145
+
<p><strong>Access control</strong>: RecordWeb deliberately defines no authorisation model. Data security and information protection are delegated to the implementing systems. The specification provides an optional <code>accessPolicy</code> block in the minimum metadata set.</p>
1143
1146
<p><strong>Federation</strong>: RecordWeb offers a directional answer inspired by DNS architecture. DID resolvers function like DNS servers: federated, replicated, without a single point of failure. The Nanopublication network <adata-link-type="biblio" href="#biblio-nanopub" title="Nanopublications: A Growing Resource of Provenance-Centric Scientific Linked Data">[NANOPUB]</a> offers a working reference model: a decentralised peer-to-peer server network in which each node holds cryptographically signed, immutable micro-assertions identified by Trusty URIs. RecordWeb <adata-link-type="dfn" href="#record" id="ref-for-record⑥⑨">Records</a> in their finalised state share the same structural properties (immutable, hash-identified, independently verifiable) and could be published and queried across a Nanopub-inspired federation layer. The complete federation architecture is the subject of <adata-link-type="biblio" href="#biblio-rwp" title="RecordWeb Protocol (RWP)">[RWP]</a>.</p>
1144
1147
<p><strong>Deletion obligations</strong>: The tension between RecordWeb’s immutability and the data protection right to erasure (GDPR, Swiss DSG) is resolved through <em>payload deletion while retaining structure</em>. On a legal requirement, the payload is deleted; the DID, the <adata-link-type="dfn" href="#metadata" id="ref-for-metadata⑤">metadata</a>, and the graph structure are retained. The <adata-link-type="dfn" href="#record" id="ref-for-record⑦⓪">Record</a> continues to exist as a provable "empty shell", its former existence is documented, its content is gone.</p>
1145
1148
<p>Depending on the specific legal basis, the deletion regime admits three distinct modes:</p>
<p>No deletion occurs, not even of the <adata-link-type="dfn" href="#payload" id="ref-for-payload③">payload</a>. Applies where a statutory retention obligation overrides the erasure claim (e.g. tax records, notarial acts, public register entries). The legal basis must be documented as <adata-link-type="dfn" href="#metadata" id="ref-for-metadata⑧">metadata</a> on the <adata-link-type="dfn" href="#record" id="ref-for-record⑦③">Record</a> at the time of creation.</p>
1156
1159
</dl>
1157
-
<p>The applicable mode is declared in the <code>deletion-regime</code> field of the <adata-link-type="dfn" href="#record" id="ref-for-record⑦④">Record</a>’s <adata-link-type="dfn" href="#metadata" id="ref-for-metadata⑨">metadata</a>. Implementations MUST respect this field and MAY enforce it at the infrastructure level.</p>
1160
+
<p>The applicable mode is declared in the <code>deletionRegime</code> field of the <adata-link-type="dfn" href="#record" id="ref-for-record⑦④">Record</a>’s <adata-link-type="dfn" href="#metadata" id="ref-for-metadata⑨">metadata</a>. Implementations MUST respect this field and MAY enforce it at the infrastructure level.</p>
1158
1161
<p><strong>Performance and scaling</strong>: A global network of linked <adata-link-type="dfn" href="#record" id="ref-for-record⑦⑤">Records</a> with cryptographic hash values places demands on infrastructure that are not yet fully foreseeable.</p>
1159
1162
<p><strong>Platform adoption</strong>: The actual adoption task lies not with the end user, but with the platform providers: Microsoft, Google, SAP, and others must integrate RWP as a native layer into their products.</p>
<td><adata-link-type="biblio" href="#biblio-iso14721" title="ISO 14721:2012 — Open Archival Information System (OAIS)">[ISO14721]</a> (OAIS)
1208
1211
<td>Complementary. RecordWeb covers the operational phase; OAIS covers long-term preservation. RecordWeb <adata-link-type="dfn" href="#record" id="ref-for-record⑨①">Records</a> can be migrated to OAIS-compliant archives with the DID retained.
1209
1212
<tr>
1210
-
<td><adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 — Information lifecycle in public administration">[ECH-0164]</a>
1213
+
<td><adata-link-type="biblio" href="#biblio-ech-0164" title="eCH-0164 Information lifecycle in public administration (V1.1, in preparation)">[ECH-0164]</a>
1211
1214
<td>Compatible. RecordWeb reinterprets the three lifecycle phases as states within a single information object, without system boundaries between them.
<dd><ahref="https://www.ech.ch"><cite>eCH-0164 — Information lifecycle in public administration</cite></a>. URL: <ahref="https://www.ech.ch">https://www.ech.ch</a>
1292
+
<dd><ahref="https://www.ech.ch/de/ech/ech-standards/ech-0164"><cite>eCH-0164 Information lifecycle in public administration (V1.1, in preparation)</cite></a>. Draft. URL: <ahref="https://www.ech.ch/de/ech/ech-standards/ech-0164">https://www.ech.ch/de/ech/ech-standards/ech-0164</a>
1290
1293
<dtid="biblio-git">[GIT]
1291
1294
<dd>Linus Torvalds. <ahref="https://git-scm.com"><cite>Git: Fast Version Control System</cite></a>. 2005. URL: <ahref="https://git-scm.com">https://git-scm.com</a>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments