...
Tammy Allgood Wolf- Melissa Anez
- Chris Awre
- Thomas Bernhart
- Danny Bernstein
- Robert Cartolano
- Aaron Choate
- Sayeed Choudhury
Stefano Cossu- Jon Dunn
- Karen Estlund
- Dan Field
- Raman Ganguly
- Jennifer Gilbert
- Babak Hamidzadeh
- Neil Jefferies
- Mark Jordan
- Danny Lamb
- Rosalyn Metz
- Este Pope
- Scott Prater
- Robin Ruggaber
- Tim Shearer
Erin Tripp- Andrew Woods
- Dustin Slater
- Jennifer Vinopal
- Evviva Weinraub
- Jared Whiklo
- David Wilcox
- Wei Xuan
- Maurice York
- Laurie Arp
- Robert Miller
...
(TS) In the mutable head scenario, is it a given that auto versioning is an option? Not a default?
(AW) I think these are orthogonal topics. If you have auto versioning on at the application or Fedora level, the mutable head directory wouldn't exist or would be empty because all content would be versioned.
(DB) Having the system just auto version makes it more simple to not have than dealing with a mutable head, but if we have a mutable head it makes on-demand versioning easier.
(SP) <asked about having unversioned content in the OCFL structure>
(AW/RS) You must not include other objects in the OCFL object root is the specification. See the last sentence in the draft https://ocfl.io/draft/spec/#object-structure
(RS) I think the language in the specification should be change from "must not" to "should not". I think it is ok to have content in a directory that hasn't been versioned.
(DW) Whatever we choose, it is going to be a compromise. What the decision gets down to is: where should unversioned content live? We want to hear from this group on what the community thinks, and what the best way forward for Fedora?
...