Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
- ? add slack channel info here?
Attendees
- 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-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.
- 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:
- 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
: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
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
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/pull/343
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