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
This version introduces editorial and scoping clarifications around standards referenced by RecordWeb:
14
+
15
+
- Clarified the description of the classical lifecycle (Section 4.3) as anchored in ISO 15489 and other national standards (e.g. Switzerland eCH-0164), instead of singling out Switzerland alone.
16
+
- Refined the discussion of ISO 15489: the section now focuses on ISO as the international foundation for RecordWeb’s requirements, with national lifecycle frameworks (such as eCH-0164) explicitly treated as jurisdiction-specific mappings defined by their respective owners.
17
+
- Removed git from the “Related Concepts” section; git is referenced only as an implementation analogy for DAGs, not as a records or archival standard.
18
+
- Updated Annex B to state that RecordWeb directly maintains only international standards (ISO, W3C, IETF, etc.) and core conceptual frameworks. National or sectoral standards MAY be listed as non-normative mappings, with relationship text supplied by the standard owners.
19
+
- Marked the relationship text for eCH-0164 in Annex B as “TBD by eCH”, making explicit that RecordWeb does not define the official mapping for this national standard. Others as "TBD by RecordWeb CG".
20
+
- Removed explicit chapter "Introduction" as the info is in the doc by W3C-Template (Status of this document).
21
+
22
+
These changes do not introduce new normative requirements. They clarify RecordWeb’s positioning: grounded in international standards, open to national mappings without structural dependency.
"title": "Structuring the Records Continuum — Part One",
88
+
"authors": ["Frank Upward"],
89
+
"date": "1996",
90
+
"publisher": "Archives and Manuscripts, 24(2), 268–285"
91
+
},
92
+
"UPWARD-1997": {
93
+
"title": "Structuring the Records Continuum — Part Two",
94
+
"authors": ["Frank Upward"],
95
+
"date": "1997",
96
+
"publisher": "Archives and Manuscripts, 25(1), 10–35"
97
+
}
110
98
}
111
99
</pre>
112
100
113
101
114
-
Introduction {#intro}
115
-
=====================
116
-
117
-
## Status of This Document ## {#status}
118
-
119
-
This document is a **CG Draft** 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.
120
-
121
-
The published baseline of this concept is available at [[ZENODO-RWC]] (DOI: 10.5281/zenodo.20475343). This working document reflects ongoing development toward the Community Group deliverable.
122
-
123
-
Feedback is invited via [GitHub Issues](https://github.com/recordweb/rwc/issues).
124
-
125
-
126
102
Summary {#summary}
127
103
=====================
128
104
@@ -260,7 +236,7 @@ The Records Continuum provides no structural answer to these questions. It descr
260
236
261
237
## The Classical Lifecycle: Structure Without Flexibility ## {#classical-lifecycle}
262
238
263
-
On the other side stands the classical lifecycle, as anchored in [[ISO15489]] and in Switzerland in [[ECH-0164]]: processing — retention — archiving or disposal.
239
+
On the other side stands the classical lifecycle, as anchored in [[ISO15489]] and other national standards (e.g. Switzerland [[ECH-0164]]): processing — retention — archiving or disposal.
264
240
265
241
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.
266
242
@@ -583,63 +559,23 @@ Tim Berners-Lee's Linked Data principles [[LINKED-DATA]] are the conceptually cl
583
559
584
560
RecordWeb is the technical implementation of the Records Continuum idea [[UPWARD-1996]][[UPWARD-1997]]. The notion that a [=Record=] does not die but lives on is structurally anchored in RecordWeb, through immutable versions, through the [=version graph=], through the absence of an "archiving" system transition.
585
561
586
-
## ISO 15489 and eCH-0164 ## {#related-iso15489}
562
+
## Records Management (RM) ## {#related-rm}
587
563
588
-
[[ISO15489]] defines international principles of Records Management: authenticity, reliability, integrity, usability. These four properties are RecordWeb's requirements specification. RecordWeb fulfils all four structurally:
564
+
RM [[ISO15489]] defines international principles of Records Management: authenticity, reliability, integrity, usability. These four properties are RecordWeb's requirements specification. RecordWeb fulfils all four structurally:
589
565
590
566
- **Authenticity**: DID and cryptographic hash guarantee that a [=Record=] is what it claims to be
591
567
- **Reliability**: [=Finalisation=] and immutable versions guarantee that a [=Record=] is complete and correct at the time of finalisation
592
568
- **Integrity**: Merkle hashes guarantee that a [=Record=] cannot change unnoticed after finalisation
593
569
- **Usability**: The DID document and [=metadata=] guarantee that a [=Record=] remains findable and accessible, regardless of system migrations
594
570
595
-
[[ECH-0164]] 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.
596
-
597
-
## OAIS ## {#related-oais}
571
+
## Open archival information system (OAIS) ## {#related-oais}
598
572
599
573
OAIS [[ISO14721]] 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 [=Records=] can be migrated to long-term archives according to OAIS principles; the DID is retained in this process.
600
574
601
575
## PROV-O ## {#related-provo}
602
576
603
577
[[PROVO]] is a W3C standard for describing the provenance and history of data. RecordWeb and PROV-O overlap in intention. The difference: PROV-O is a description standard, it can be layered onto existing systems. RecordWeb is an architecture standard, provenance is structurally anchored in the [=version graph=]. PROV-O would be a possible serialisation format for RecordWeb lineage documentation.
604
578
605
-
## Git ## {#related-git}
606
-
607
-
[[GIT]] internally uses the same DAG approach as RecordWeb: every commit is an immutable snapshot, linked to its predecessors, identified by a cryptographic hash.
608
-
609
-
RecordWeb learns from [[GIT]]: the immutability of commits, the explicitness of branches and merges, the cryptographic securing through content hashes. The difference: [[GIT]] is for code and files, not for semantic information objects with institutional accountability. [[GIT]] knows no states, no [=record owner=], no classification, no schema. RecordWeb adopts the fundamental technical logic of [[GIT]] and transfers it into the institutional context.
610
-
611
-
## Summary: Positioning of RecordWeb ## {#positioning-summary}
<td>Conceptually compatible. RecordWeb provides a technical architecture that makes the normative requirements (authenticity, reliability, integrity, usability) implementable.</td>
691
+
<td>TBD by RecordWeb CG.</td>
756
692
</tr>
757
693
<tr>
758
694
<td>ISO 30300</td>
759
-
<td>Complementary. ISO 30300 defines who is responsible; RecordWeb defines how responsibility is structurally anchored.</td>
695
+
<td>TBD by RecordWeb CG.</td>
760
696
</tr>
761
697
<tr>
762
698
<td>[[ISO14721]] (OAIS)</td>
763
-
<td>Complementary. RecordWeb covers the operational phase; OAIS covers long-term preservation. RecordWeb [=Records=] can be migrated to OAIS-compliant archives with the DID retained.</td>
699
+
<td>TBD by RecordWeb CG.</td>
764
700
</tr>
765
701
<tr>
766
702
<td>[[ECH-0164]]</td>
767
-
<td>Compatible. RecordWeb reinterprets the three lifecycle phases as states within a single information object, without system boundaries between them.</td>
703
+
<td>TBD by eCH.</td>
768
704
</tr>
769
705
<tr>
770
706
<td>[[DID-CORE]]</td>
771
707
<td>RecordWeb uses DIDs as the basis for [=Record=][=identity=] and is fully compatible with the W3C DID standard.</td>
772
708
</tr>
773
709
<tr>
774
710
<td>[[PROVO]]</td>
775
-
<td>PROV-O could be used as a serialisation format for RecordWeb lineage documentation to establish interoperability with PROV-O-compatible systems.</td>
711
+
<td>PROV-O would be used as serialisation format for RecordWeb lineage documentation to establish interoperability with PROV-O-compatible systems.</td>
0 commit comments