Powered by OPF
OPF WIKI STATIC ARCHIVE
See the original ↗Page history
2,681 pages · 153 spaces · 776 tags · 4,025 history records · 96.2% of the original wiki recovered
Archived copy. This page was recovered from the Internet Archive snapshot of /pages/viewpage.action?pageId=11337748 taken on 2019-11-19. The original wiki at wiki.opf-labs.org is being decommissioned.

OPF File Format Risk Registry

Created by Andrew Jackson on Dec 20, 2011 · last edited by Johan van der Knijff · on Mar 03, 2014 (view history) · 21 versions
The OPF File Format Risk Registry provides a reference guide to file format-specific risks that have implications for long-term preservation and accessibility.
To add a new Format Registry entry, follow this link.
Don't forget to add labels to your new Format Registry entry by clicking on the "Edit" text next to "Labels" at the bottom of the screen.

File Format Risks

Registry scope

The File Format Risk Registry is focused on these four aspects:

  • What are the main issues associated with this format?
  • How does each issue affect long-term accessibility? What are the risks?
  • For each issue, how can we assess whether a file object is affected, and using which tool(s)? How do we measure the risks?
  • Are there any recommendations for dealing with an issue, or for mitigating its impact?

Relation to institutional policies

Institutions may have policies that define how the issues that are described in this registry are dealt with. In that case identified errors/risks need to be validated against the low-level institutional policy (control policy). There are a number of ways to achieve this. The following 2 blog posts present a straightforward approach that is based on Schematron rules:

Relation to other format registries

A number of format registries already exist, such as PRONOM, the ArchiveTeam File Formats Wiki and UDFR. Unlike those registries, the OPF FFRR focuses specifically on issues and risks, and how to deal with these in a practical way. So the information provided by FFRR should be seen as complementary to these more formal format registries. Being a Wiki, FFRR is also more free-form than PRONOM or UDFR. That aside, the very nature of its content isn't well suited to a more formalised database-centred approach.