...
Pull requests:
- NEW: 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)
- pr-325 - Making location headers a MUST in post responses for ldpcv's (needs discussion)
pr-320 - Add section on ACL Representation and Interpretation (awaiting input from Benjamin Armintor)Mergedpr-318 - Say LDP-RS must be created with LDP-NR on PUT (awaiting input from Benjamin Armintor)Merged
Plan for addressing open Recommendation issues
- Open No Milestone issues
Notes
Much of the conversation focused on: https://github.com/fcrepo/fcrepo-specification/pull/326
- 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
Action Items
- ACTION (Daniel Lamb): To create PR: non-norm: LDPCv is both a timemap and a container, but does not allow POST
- Andrew Woods to schedule Editors / Implementers conversation series