Page History

...

1. What representation should be used for resources on disk?
   1. Some examples here https://gist.github.com/bbpennel/3dd2ec19d3545e0417071958177baa93
2. Automatically generated checksums
   
   1. OCFL will generate a digest automatically for storage reasons (not necessarily always the same algorithm), should this be surfaced in Fedora? 
      1. We probably want to do this but we should check in with Aaron Birkland  first to verify that this is what we want.
      2. Should the digests included in existing OCFL objects be surfaced in fedora?  
3. Canonicalization of RDF,  checksumming metadata, and the possibility of byte-for-byte I/O of metata resources.
   1. Is this of use: http://json-ld.github.io/normalization/spec/index.html
4. Converter framework:  should it stay or should it go?
5. Should we evaluate a "Minimal" Fedora 3 migration, where all datastreams from a fcrepo3 object are placed into a single OCFL object with no modifications?
6. Autoversioning -
   
   1. Configurable repository wide?
   2. Or configurable by object, similar to fedora 3? REST API#modifyDatastream (versionable param)
7. Is there a use case for minting multiple versions within a transaction?  Are the technical challenges for supporting that worth the effort?
8. Tombstones handling:
   1. If you delete an AG, does the whole OCFL object go away?
   2. We will continue to support Tombstones no? In that case, the OCFL Object would only go away once all the tombstone's were deleted.
   3. If /my-ag is deleted, would we expect /my-ag/binary1/fcr:tombstone to exist?
   4. Then if we delete /my-ag/fcr:tombstone would we expect all tombstones of the children also to be deleted, ie /my-ag/binary1/fcr:tombstone?

...