...
- 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 ReportReport https://jira.duraspace.org/issues/?filter=14401
- Memento-Datetime header granularity issue RFC-1123
- 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 method call (setProperty(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-1123
- 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?
Sprint tickets
Jira | ||||||
---|---|---|---|---|---|---|
|
Ticket Summaries
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
Separate tickets
- Creating Mementos when not providing Memento-Datetime
- no body
- Converting dynamic properties to static properties
Other
- ACTION: BenP to submit an initial, minimal PR for creating no-body LDPRv's
Updates from spec editors meeting
...
Regarding 2.a:
- Two options:
Reduce the granularity of our label
Modify Memento spec
- Consensus on option 1.
- Return 409 when timestamps conflict.
- Agreement that server-managed or distributed backends could have trouble with that
https://jira.duraspace.org/browse/FCREPO-2727 & https://jira.duraspace.org/browse/FCREPO-2728
Bethany Seeger & awoods:
Memento Tools - Validator: http://mementoweb.org/tools/validator/
Regarding 2c: Consensus seems to be that we should plan to that pull the webac out of the modeshape layer and handle it at the http layer. That would both solve the problem with supporting acl:Append and reduce our dependency on modeshape paving the way for swapping it with something else.
Regarding 3. external content pr
...
: https://github.com/fcrepo/fcrepo-specification/
...
Use POST/PUT requests to create external content nodes.
Consensus on proposed API changes.
Action Items
- Danny Bernstein determine whether there is any case where a PUT on a TimeMap would make sense. If there is it should be raised with the specification editors.
- Peter Eichman to do a short 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. ACL Agents - Strings vs. URIs