Skip to content
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.

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

Make it clear that the fixity block may not contain fixity for all files in an object #408

Closed
zimeon opened this issue Nov 19, 2019 · 0 comments · Fixed by #409
Closed
Assignees
Labels
Editorial Editorial issues (no changes to intent) OCFL Object
Milestone

Comments

@zimeon
Copy link
Contributor

zimeon commented Nov 19, 2019

Split from #406: we need to make it clear that the fixity block may not contain fixity for all files in a version or object. The manifest serves this purpose, MUST be complete, and is the canonical fixity information for all content files. The fixity block is an optional convenience for storing additional fixity values, typically from migrations. It is also optional whether fixity information is carried forward from one version to another.

@zimeon zimeon added Editorial Editorial issues (no changes to intent) OCFL Object labels Nov 19, 2019
@zimeon zimeon added this to the 1.0 milestone Nov 19, 2019
@zimeon zimeon self-assigned this Nov 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Editorial issues (no changes to intent) OCFL Object
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant