Hi Oliver, Can you provide a bit more detail about what you are looking for?
I think what is unclear to me is whether you are speaking about multiple Oak instances or just one. I’m guessing what you have in mind is something like one Oak instance can write to a repo, and a second Oak instance can access the repo read-only, thus allowing the second to present the content but also achieve the “revision-/audit-proof” requirement. If that resembles what you have in mind, the next question is whether the second Oak instance needs to also support making changes in a separate repository or whether it should be strictly read-only. If that’s not what you were thinking of can you please explain it in a bit more detail? HTH -MR On April 10, 2018 at 3:07:27 AM, Oliver Lietz (apa...@oliverlietz.de) wrote: hi, I'm looking for info how to use Oak in a revision-/audit-proof manner to archive versioned assets in a (read-only) repo. The only related document I've found so far is the talk "Binary Data Management Features in Oak 1.8" from Matt and Conrad. Any other sources or ideas? Thanks, O.
