...

1. Addressing External Content: Redirect or Proxy?
   1. I believe we have landed on a solution... just need a PR
   2. https://github.com/fcrepo/fcrepo-specification/issues/338
   3. pr-343 - message/external-body -> Link header
   4. issue-338 - Define custom headers for external content requests
   5. issue-344 - Add Accept-External-Content-Scheme header? 
   6. issue-308 - Clarify expectations around external body content and Accept-Post response header
   7. Question: How to support LDP-NR headers on GET and HEAD for `redirect` handling?

2. Pull requests:

   Pull requests:

   pr-340 - Prefer headers request not require - (Need review from Daniel Lamb and Benjamin Armintor)
   1. pr-334 - Add version number to specification title (let it sit until 1.0 release date)
   Plan for addressing open Recommendation issues
3. 1. #308 - Requiring Accept-Post on OPTIONS, recommending for GET/HEAD -  PR #337 has been somewhat overtaken by ongoing debate about external content
   New issues?
4. Tidying and reviewing the spec

Notes

Actions from 2018-03-07 - API Spec Meeting

1. External Content
   1. PR-343: Andrew Woods and Daniel Lamb to approve pending minor updates from review.
   2. ISSUE-344: No objections, pending PR-343, but noted that we might be bloating the headers a little bit.
   3. ISSUE-308: Will be resolved via PR-343
   4. Andrew Woods to make an issue for "How to support LDP-NR headers on GET and HEAD for `redirect` handling?" - done: issue-345
2. Spec Test Suite
   1. Some of the links of have been updated to point to the Draft spec, and an additional PR was made recently.
•  Simeon Warner will update PR 341:
  •  require handling parameter
  •  add Accept-External-Content-Handling response header
•  Esmé Cowles will update Issue 338 with a summary of our discussion
•  ALL: review PR 341 once updated