version example missing manifest listing?

[bseeger]

In the version example of an OCFL object, it seems like 'example2.txt' might be missing from the manifest listing. It should be there, correct?

https://ocfl.io/draft/spec/#example-versioned-object

Thanks!

[ahankinson]

Nope. "empty2.txt" is a copied version of "empty.txt", and in v3, "empty.txt" is 'deleted' from the state. So the logical file 'empty2.txt' has the same content state as the physical file 'empty.txt', as signified by them having the same hash.

Essentially, the manifest hashes indicate where a client can resolve the content from, independently of the filename assigned to it in any given version.

[ahankinson]

Also, since there is no physical change to the state, the version directories do not need to hold physical files. So while there is a version 3 in state, there is actually no new content. That's why 'empty2.txt' never appears in any version folder.

[zimeon]

I agree with @ahankinson that the example is correct. This example was generated from the example v1/2/3 state in https://github.com/OCFL/fixtures/tree/master/1.0/content/spec-ex-full using the procedure described in https://github.com/zimeon/ocfl-py/blob/master/README_build_spec_example.md . However, the ocfl-py code was out-of-date: modifications had been made to the example in the spec by-hand. I have updated ocfl-py to bring it up-to-date with the use of type in the current spec (see #232) and the move of fixtures into a 1.0 dir, and have verified that it again generates exactly the spec example.

[awoods]

I concur with @ahankinson and @zimeon 's responses.

@bseeger , are you still pondering some aspect of this? If so, let's discuss. Otherwise, please feel free to close the issue.

[bseeger]

No - this makes much more sense to me now. Thanks for the clarification on the example.