...
- Authorization issues
- #176 resolved-needs pr
- #175: clarify SOLIDWEBAC's position, and whether it is satisfied by virtue of being LDP-RS
- #172 remains open
- #170 thumbs and comments
- #165
- Versioning Issues
- #130 needs pr
- #187 simeon doesn't understand suggestion so far (and doesn't like probes that change repo content) but maybe covered by #186
- #186 do we agree on the OPTIONS pattern, how to spec?
- #185 agreement that implementations must support versioning (client or server managed) → PR #188
- we need to run the 2-step process for detecting versioning model past middleware implementers
Minutes
Action Items
- All to read up on
- Versioning
- #130: Simeon will make a PR
- Vocab PR too
- #185:
- #130: Simeon will make a PR
- fcrepo.
- io
- com/fcrepo/fcrepo-specification/pull/188 is approved by Simeon & Esmé
- What does versioning of external content mean? Maybe more of an audit log?
- Some uncertainty about whether versions should be required, and whether they are being used by e.g., Islandora and Samvera.
- 186: we may need some non-normative language to clarify how a client know whether it can create version, or whether the server will create them
- Esmé will check the spec to see if there is good language there, and add a PR to improve if not, the basic approach is:
- HEAD on a resource to find TimeMap
- OPTIONS on the TimeMap to see if versions can be created by the client
- if so, it can create versions if desired
- if not, then the server is responsible for creating them
- Esmé will check the spec to see if there is good language there, and add a PR to improve if not, the basic approach is:
- com/fcrepo/fcrepo-specification/pull/188 is approved by Simeon & Esmé
Action Items
- /#resource-authorization and SOLIDWEBAC Benjamin Armintor to ask Hydra stakeholders about recursive deletion expectations
- Simeon Warner to make PRs for #130
- Esmé Cowles to review #186 and create PR as needed to clarify language