...
- Danny Bernstein
- Bethany Seeger
- Jared Whiklo
- Peter Eichman
- Andrew Woods
- Yinlin Chen
- Esmé Cowles
- Doron Shalvi
- Kevin Ford
- Randall Floyd
- Carrick Rogers
- David Wilcox
- Ben Pennell
Aaron Birkland- Joe Harrington
Daniel Lamb
Agenda
- Welcome to new Fedora Committer: Yinlin Chen
- Alignment Sprint 1 Progress Report https://jira.duraspace.org/issues/?filter=14401
- Memento-Datetime header granularity issue RFC-2295
- The memento spec does not support version sub-second granularity
- There is no problem with us supporting it internally (when creating mementos without specifying the header).
- However is we support sub-second granularity it is not clear how we will be able to import versions without losing information.
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2710 - Challenges with acl:Append
- https://fcrepo.github.io/fcrepo-specification/#append-ldprs
- The spec defines rules at the HTTP method layer while the ACLs are implemented in the jcr layer.
- It makes it difficult to determine whether a POST, PUT or PATCH has occurred and whether a node existed when the transaction began.
- The javax.jcr.Node interface uses the same permsission (org.modeshape.jcr.SET_PROPERTY) for adding, updating and removing properties and generates the same:
- reference tickets:
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2715 Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2716 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2717
- 5.7.3 LDP-NR - Patching Binaries (LDP-NR) - do we plan to support?
- Memento-Datetime header granularity issue RFC-2295
- Specification of External Content interaction
Code Block :Request: Link: <some-URI>; rel="http://fedora.info/definitions/fcrepo#ExternalContent"; type="image/jpeg"; handling=<copy|redirect|proxy> :Response: Content-Location: <some-URI> Content-Type: image/jpeg :Fedora advertising support: OPTIONS Accept-External-Content-Handling: <copy|redirect|proxy> :Comma separated list like Accept, if supporting multiple handling approaches:
- Feedback on Peter Eichman's writeup on the use of userAgent and groupAgent base URI's and their relationship to WebAC in order to clarify whether or not what if anything needs improvement/clarification/alignment
...