-
Notifications
You must be signed in to change notification settings - Fork 14
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
must a manifest entry be referenced in at least one version's state #537
Comments
Suggested resolution:
|
Proposing a PR with minor wording change from the above:
|
There are three parts to the agreed solution, #561 does only part 1. Still need parts 2 & 3. |
OCFL/fixtures#97 is part 2, OCFL/fixtures#98 is part 3. Complete and can close when both merged |
Fixture E050_file_in_manifest_not_used, is a test for a manifest entry that is not referenced in any version state. It specifies the error should be
E050
:That text states that every logical path MUST have a corresponding manifest entry. It does not state that ever manifest entry MUST have at least one corresponding logical path. The nearest I can find to such a requirement in the spec is:
But, that line, besides not having an associated validation code, is ambiguous. If "versions" are version objects in the inventory, then that could be read as requiring that every manifest entry be references in at least one version's state. But, if "versions" are version directories on disk, then it doesn't seem to be a requirement at all.
The text was updated successfully, but these errors were encountered: