{
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "The specification describes objects at rest; atomic updates and recovery procedures require implementation choices.",
      "citationIds": [
        "spec",
        "notes"
      ]
    },
    {
      "text": "OCFL does not portably preserve filesystem permissions or timestamps and prohibits hard and symbolic links; preserving such features requires a suitable disk or filesystem image stored as a regular file.",
      "citationIds": [
        "spec"
      ]
    }
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "slug": "oxford-common-file-layout",
  "term": "Oxford Common File Layout",
  "aliases": [
    "OCFL",
    "OCFL object"
  ],
  "definition": "Oxford Common File Layout is a storage layout for versioned digital objects that maps logical file names to stored content through a digest-based inventory.",
  "note": "In OCFL 1.1, the object-root inventory.json records the object identifier, latest version, content manifest and version states. The manifest maps digests to stored content paths; each version's state maps those digests to logical file names. Stored paths and logical names can differ. [spec]\n\nA later version can reference content stored in an earlier version, so a version directory need not be a self-contained copy. Previous versions should remain immutable; removing old content can break newer states. [notes]\n\nThe optional fixity block carries supplementary digests and may cover only some files. It does not replace the mandatory manifest or make payload checking optional. [spec]\n\nValidating an object establishes its internal consistency, not that it is the intended recovery target. For recovery, retain an independent version expectation and still verify the payload. [evidence]",
  "related": [
    "backup-manifest",
    "content-addressed-storage",
    "checksum",
    "restore-test",
    "bagit"
  ],
  "citations": [
    {
      "id": "spec",
      "title": "OCFL 1.1 specification: inventories, versions, fixity and objects at rest",
      "url": "https://ocfl.io/1.1/spec/",
      "accessed": "2026-11-21"
    },
    {
      "id": "notes",
      "title": "OCFL 1.1 implementation notes: content paths, version immutability and updates",
      "url": "https://ocfl.io/1.1/implementation-notes/",
      "accessed": "2026-11-21"
    },
    {
      "id": "evidence",
      "title": "Hesela: OCFL object validation and independent recovery-target checks",
      "url": "https://hesela.com/analyses/backup-verification-is-not-a-restore-test/#ocfl-recovery-target",
      "accessed": "2026-11-21"
    },
    {
      "id": "paper",
      "title": "Hankinson et al. (2019): The Oxford Common File Layout: A Common Approach to Digital Preservation",
      "url": "https://doi.org/10.3390/publications7020039",
      "accessed": "2026-11-21"
    }
  ],
  "provenance": [
    "Source synthesis of OCFL 1.1; logical names, physical content and additional fixity digests are distinct concepts. [spec]",
    "The existing seven-fixture recovery study uses pinned ocfl-py 2.1.0. This definition does not extend those observations to other implementations. [evidence]",
    "The 2019 design paper describes an alpha specification and compares metadata-access operations, not full payload validation or current restore performance. Use OCFL 1.1 for the format rules here. [paper]"
  ]
}
