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
(facilitator)
(notetaker)
Benjamin Armintor
Esmé Cowles
Daniel Lamb
Andrew Woods
Simeon Warner
Agenda
Addressing
External Content: Redirect or Proxy
?
I believe we have
landed on a solution
... just need a PR
https://github.com/fcrepo/fcrepo-specification/issues/338
Pull requests:
pr-340
- Prefer headers request not require - (
Need review from
Daniel Lamb
and
Benjamin Armintor
)
pr-334
- Add version number to specification title
(
let it sit until 1.0 release date
)
Plan for addressing open
Recommendation
issues
#308
- Requiring Accept-Post on OPTIONS, recommending for GET/HEAD -
PR
#337
has been somewhat overtaken by ongoing debate about external content
New issues?
Tidying and reviewing the spec
Notes
PR 340: is simpler than it looks, needs review from
Daniel Lamb
and
Benjamin Armintor
PR 341: have consensus, need review from all
Do we want handling to be a Prefer, or mandatory?
Probably mandatory — people probably know how they want it to work, and would rather have a failure than a different handling option
We can add other parameters to the Link header
Accept-External-Content-Handling header in OPTIONS response to advertise which handling options are supported
What if the client doesn't supply a handling parameter?
It should be required — the client can check the OPTIONS response and decide what handling it wants
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