Page History

...

This design of Fedora OCFL objects is narrowly focused on the logical state of the OCFL object. Details such as content paths and how OCFL objects are physically represented on disk are OCFL implementation details and are not covered.

Definitions

1. Atomic resource: A Fedora resource (a binary or container) that maps to a single OCFL object
2. Archival group
3. Header file

Basic OCFL Structure

...

...

1. : A potentially hierarchical set of Fedora resources (binaries and/or containers) that maps to a single OCFL object
2. Archival part: A Fedora resource (a binary or container) that is a constituent part of an archival group

Basic OCFL Structure

The following is an example of an OCFL object that contains two versions, consisting of a hierarchy of files and directories. For more information on OCFL, see the specification.

[object root]
    ├── 0=ocfl_object_1.0
    ├── inventory.json
    ├── inventory.json.sha512
    ├── v1/
    │   ├── inventory.json
    │   ├── inventory.json.sha512
    │   └── content/
    │       ├── empty.txt
    │       ├── foo/
    │       │   └── bar.xml
    │       └── image.tiff
    └── v2/
        ├── inventory.json
        ├── inventory.json.sha512
        └── content/
            └── foo/
                └── bar.xml

Basic Fedora OCFL Structure

The following is how Fedora (as an archival group) would represent the above example:

[object root]
    ├── 0=ocfl_object_1.0
    ├── inventory.json
    ├── inventory.json.sha512
    ├── v1/
    │   ├── inventory.json
    │   ├── inventory.json.sha512
    │   └── content/
    │       ├── empty.txt
    │       ├── foo/
    │       │   └── bar.xml
    │       └── image.tiff
    └── v2/
        ├── inventory.json
        ├── inventory.json.sha512
        └── content/
            └── foo/
                └── bar.xml

..diagrams:
- atomic with two versions of a binary
- atomic with two versions of a container
- archival group with two versions of a nested container with a binary

...