Skip to content

clarify what metadata and content means #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zimeon merged 2 commits into from
Dec 4, 2025
Merged

clarify what metadata and content means #667

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4d5b788
clarify what metadata and content means
rosy1280 Aug 14, 2025
9ad4f45
line length changes
rosy1280 Aug 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions draft/spec/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,11 +69,12 @@ versioning, robustness, and storage diversity.
#### Completeness
{:.no_toc #completeness}

The OCFL recommends storing metadata and the content it describes together so the OCFL object can be fully understood in
the absence of original software. The OCFL does not make recommendations about what constitutes an object, nor does it
assume what type of metadata is needed to fully understand the object, recognizing those decisions may differ from one
repository to another. However, it is recommended that when making this decision, implementers consider what is
necessary to rebuild the objects from the files stored.
The OCFL recommends storing metadata (this includes all types of metadata; e.g., technical, structural, descriptive,
etc.) and the content (e.g., images, text files, etc.) it describes together so the OCFL object can be fully
understood in the absence of original software. The OCFL does not make recommendations about what constitutes an
object, nor does it assume what type of metadata is needed to fully understand the object, recognizing those
decisions may differ from one repository to another. However, it is recommended that when making this decision,
implementers consider what is necessary to rebuild the objects from the files stored.

#### Parsability
{:.no_toc #parsability}
Expand Down