Time/Place
- Time: 2:30pm Eastern Time US
- 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
Attendees
(notetaker)
Agenda
Editors / Implementers meeting:
Thursday, Feb 22nd @1pm ET
- Compatibility test suite usage updates?
Pull requests:
- pr-329 - Editorial change: Reordering of Authorization subsections (needs review from all)
- pr-326 - Loosening requirements on rel=type link headers for PUT when type is (awaiting response from Daniel Lamb)
- There is friendly debate on whether this section should be included at all
- The general issue is: do we want to specify the ability to change LDP Types (i.e. interaction models)?
- And if, yes: do we want to specify the mechanism by which that is done?
- It would be great to get Simeon Warner's and Esmé Cowles' voices in the conversation
- pr-325 - Making location headers a MUST in post responses for ldpcv's (needs discussion)
Plan for addressing open Recommendation issues
- All assigned
- #310 - Accept-Post reference incorrect
- #308 - Requiring Accept-Post on OPTIONS, recommending for GET/HEAD - resolved-needs-PR
- #280 - Versioning scheme of spec - resolved-needs-PR
- Open No Milestone issues
Notes
Editors / Implementers meeting: Thursday, Feb 22nd @1pm ET
- Esmé Cowles will not be able to make it, Simeon Warner will be UK and will try to make it but no guarantees, others should be able to
- What do we want to get out of this meeting?
- Better community understanding of issues by answering questions, from which we might get clues about things in the spec that aren't clear
- Keep focus within the scope of the effort, start with framing of scope/charter/goals and desire to help implementers understand spec (not a forum to reopen issues, that should happen on github)
- Want to make timelines clear, hope to land spec in April and would like to help implementers make the same timeline
- Compatibility test suite usage updates?
- Simeon had some discussion with Jorge about running against trilpy, many failures however
- Esme did try it a couple of weeks ago
- We should all try to interact on the public fedora-api-test-suite channel
Pull requests:
- pr-329 - Editorial change: Reordering of Authorization subsections (needs review from all)
- No changes, just reordering
- Needs review from Daniel Lamb and Benjamin Armintor
- pr-325 - Making location headers a MUST in post responses for ldpcv's (needs discussion)
- Agreement to keep just first sentence about POST being optional in this situation
- Done...
- pr-326 - Loosening requirements on rel=type link headers for PUT when type is (awaiting response from Daniel Lamb)
- Agreement that support for changing types is MAY (and not MUST), and that SHOULD for the sub-class issue
- Agreement on "Impementations MAY allow the interaction model to be changed by specification of a new LDP type in a Link header. If supported, requests SHOULD be rejected unless the new LDP type specified is a sub-type the current type."
- pr-329 - Editorial change: Reordering of Authorization subsections (needs review from all)
Plan for addressing open Recommendation issues
- All assigned
- #310 - Accept-Post reference incorrect
- #308 - Requiring Accept-Post on OPTIONS, recommending for GET/HEAD - resolved-needs-PR
- #280 - Versioning scheme of spec - resolved-needs-PR
- Open No Milestone issues
Action Items
- ACTION (Daniel Lamb): To create PR: non-norm: LDPCv is both a timemap and a container, but does not allow POST