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:
The keys of [the “state” JSON object] are digest values, each of which must correspond to an entry in the manifest of the inventory.
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:
The value of the manifest key is a JSON object, with keys corresponding to the digests of every content file in all versions of the OCFL Object.
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.
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.