You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Time/Place

Attendees

(plus) (facilitator)
(star)(notetaker)

Agenda

  1. Addressing External Content: Redirect or Proxy?
    1. pr-343 - message/external-body -> Link header
    2. issue-338 - Define custom headers for external content requests
    3. issue-344 - Add Accept-External-Content-Scheme header? 
    4. issue-308 - Clarify expectations around external body content and Accept-Post response header
    5. Question: How to support LDP-NR headers on GET and HEAD for `redirect` handling?
  2. Pull requests:

    1. pr-334 - Add version number to specification title (let it sit until 1.0 release date)
  3. New issues?
  4. Tidying and reviewing the spec

Notes

  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?"
  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.

Actions from 2018-03-07 - API Spec Meeting

      • 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


  • No labels