...

1. Do we see any weaknesses in the design?
2. Is the current state of the java ocfl client sufficient to implement the design as it is? 
3. Any significant performance issues anticipated? 
   1. Mitigation strategies?
4. How do we handle versioning within a transaction? 
   1. We do not allow it (405)
   2. We allow it but reject subsequent requests  - ie the version creation request must be the last within a transaction
   3. Other possibilities ?

Notes

1. Current OCFL client does copy and not move.  Move is riskier.
   1. mv will perform better
   2. Peter Winckles  can add a mv option, but it must be recognized that there is some risk.
2. Checksumming: currently 2 checksumming operations are required by the client - a checksum could be provided to reduce that to 1  checksum calc.
   1. Peter Winckles  can add support for providing a checksum upfront.
3. We might consider making transaction committal (optionally)