Preservation standards and evidence
Standards → controls → workflows → contracts → evidence. Reference design mappings rather than Trusted Records certification.
Standards, controls and evidence matrix
| Source/version | Control | Workflow/interface | Contract | Evidence required | Status |
|---|---|---|---|---|---|
| ISO 15489-1:2016 ↗ Records management | Registration, accountability, retention/holds and disposition decisions | Official records management | declare | Versioned decisions, authority and history | Design mapping; conformance not verified |
| ISO 23081-1:2017 ↗ Records metadata | Schemas, provenance, context and lineage | Metadata and classification | metadata | Metadata mappings, sources and change history | Design mapping; conformance not verified |
| ISO 14721:2025 / OAIS ↗ Preservation model | Submission, archival and dissemination packages; designated community | Preservation Profile Center | preserve | Manifests, representation information and archive responsibilities | Design mapping; conformance not verified |
| ISO 16363:2025 ↗ Repository assessment | Organizational governance, digital objects, infrastructure and risks | Storage and data preservation | N/A | Assessment records and remediation plans; no certification verified | Design mapping; conformance not verified |
| PREMIS 3.0 / METS profile ↗ Preservation metadata / package structure | Objects, events, agents, rights and profile-specific package structure | Preservation Profile Center | preserve | Fixity/migration events; XML mapping not verified | Design mapping; conformance not verified |
| ISO 19005-4:2020 / PDF/A-4 ↗ Document format | Choose profiles by record class and validator; do not automatically convert signed originals | Conversion and migration | N/A | Validator reports, source objects and conversion lineage | Design mapping; conformance not verified |
| RFC 4998 / RFC 6283 ↗ ERS / XMLERS | Integrity and existence evidence under an agreed profile | LTANS and evidence-preservation integration | verify | Evidence records, verification reports and renewal history | Design mapping; conformance not verified |
| ETSI TS 119 511 V1.2.1 (2025-10) ↗ Preservation policy/security | Policies, practice statements, profiles, storage and termination | LTANS — long-term evidence preservation | N/A | Provider policies/profiles, controls and validation records | Design mapping; conformance not verified |
| ETSI TS 119 512 V1.2.1 (2023-05) ↗ Preservation protocols | Requests, evidence exchange, retrieval and verification | LTANS and evidence-preservation integration | preserve | Contracts/profiles and interoperability traces; backend not tested | Design mapping; conformance not verified |
Linked interfaces are reference experiences. Operations are proposed contracts rather than provider-standard APIs. Full-clause ISO review was not performed; official abstracts/metadata were used. No certification is claimed.
Source versions and status
Matrix versions were checked against ISO, ETSI, IETF and Library of Congress sources on 8 October 2026. ETSI has draft EN 319 511/512 tracks; published TS documents are references, not a claim that drafts are issued standards. Contract profiles must fix versions and review successors before go-live. No repository/Records certification evidence was received.
Official sources
| ID | Document |
|---|---|
| LAW-PDP-DECREE | 356/2025/NĐ-CP ↗ |
| LAW-ARCH | 34/VBHN-VPQH · Archives Law ↗ |
| LAW-ARCH-DECREE | 113/2025/NĐ-CP ↗ |
| LAW-ET | 36/VBHN-VPQH · Electronic Transactions Law ↗ |
| LAW-PDP | 91/2025/QH15 ↗ |
| LAW-SIGN | 23/2025/NĐ-CP ↗ |
| ISO-RM | ISO 15489-1:2016 ↗ |
| ISO-META | ISO 23081-1:2017 ↗ |
| ISO-OAIS | ISO 14721:2025 ↗ |
| ISO-PDFA | ISO 19005-2:2011 ↗ |
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment