Time/Place
- Time: 2:30pm Eastern Time US
- Dial-in Number: (712) 775-7035
Attendees
(facilitator)
(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-328 - Explicitly stating that POST may be disallowed despite inheritance (suggested wordsmithing and awaiting input from Benjamin Armintor)
- 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
- #315 - Does versioning containers violate the single-containment principle?
- #316 - Recursive delete and constraints/messaging - 3 weeks since last comment
Notes
Action Items
- ACTION (Daniel Lamb): To create PR: non-norm: LDPCv is both a timemap and a container, but does not allow POST