clarify what metadata and content means #667
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We’ve found that institutions often assume OCFL is opinionated about the internal structure of an object, despite the introduction stating explicitly that OCFL does not define an object’s structure (i.e., what makes an object an object).
One reason for this misunderstanding may be our loose use of the terms’ metadata’ and ‘content’ in the introduction (I’ll take the blame for that). In practice, when people see “metadata,” they often think only of descriptive metadata. However, metadata can also refer to other types, such as METS, which encompasses both structural and administrative metadata, or MIX, which captures technical metadata about an image.
The changes here aim to clarify that we mean all forms of metadata, not just descriptive, so that users better understand OCFL’s scope.