Time/Place

Attendees

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

Agenda

  1. Remote content and the lack of support for Digest headers in common webservers
    1. Require support for external content with access-type=url - pending review from Daniel Lamb and Benjamin Armintor
      1. https://github.com/fcrepo/fcrepo-specification/pull/242
      2. https://github.com/fcrepo/fcrepo-specification/issues/237
  2. Versioning issues
    1. "Prohibit PATCH on LDPCv"
      1. https://github.com/fcrepo/fcrepo-specification/pull/244
      2. Establish consensus on approach... currently a diversity of opinions
    2. Propose the addition of new terms to the LDP namespace

      1. https://github.com/fcrepo/fcrepo-specification/issues/245
    3. Clarify reliable method to write into LDPCv

      1. https://github.com/fcrepo/fcrepo-specification/issues/250
      2. We seem to be contradicting ourselves
    4. Include `Vary` header in LDPRv `OPTIONS` response

      1. https://github.com/fcrepo/fcrepo-specification/issues/246
    5. Added text for HEAD and GET requests to LDPCv objects - related to #244
    6. What are the semantics of version restoration?
      1. https://github.com/fcrepo/fcrepo-specification/issues/238
      2. Consensus: drop version restoration and use ingest-by-reference instead
  3. Misc PRs and Issues

    1. Adding section clarifying acl:Append - pending review from Benjamin Armintor and Daniel Lamb - merged
    2. Add section on ACL linking on resource creation - pending review from Benjamin Armintor
      1. https://github.com/fcrepo/fcrepo-specification/pull/214
      2. https://github.com/fcrepo/fcrepo-specification/issues/176
    3. Torching Depth header in lieu of advertising recursive DELETEs
      1. https://github.com/fcrepo/fcrepo-specification/pull/241
      2. https://github.com/fcrepo/fcrepo-specification/issues/234
    4. Use Location header for ingest-by-reference
      1. https://github.com/fcrepo/fcrepo-specification/issues/236
      2. Looks good, needs a PR

Notes

  1. Agreement that we will follow the process for approval (majority +1, no -1, wait 3 days) more closely now rather than waiting around for everyone. Otherwise we won't be able to get things out before Thanksgiving. We can always create new issues to debate again if necessary...
  2. Agreement to use the "Candidate Recommendation" milestone to flag issues that we need to resolve to get the next version out
    1. ACTION - all to flag issues an mark those that should be part of the milestone (by COB 2017-11-01)
  3. Remote content and the lack of support for Digest headers in common webservers
    1. Require support for external content with access-type=url - pending review from Daniel Lamb and Benjamin Armintor
      1. https://github.com/fcrepo/fcrepo-specification/pull/242
      2. https://github.com/fcrepo/fcrepo-specification/issues/237
    2. Discussion of whether should have MUST for creation of external resources via API, and if so, how similar the requirements are for supporting them in a similar way to internal resources
    3. Convern that standard servers (apache, nginx, s3) do not give digest headers so implementation of `Want-Digest` would require the Fedora to download complete content and checksum it. This is a significant overhead. However, the idea of having external content proxied as a Fedora object is that it behaves like a real Fedora object, different from a reference to an external resource. Feeling on call is that we should retain the MUST support Want-Digest with the understanding that the implementation might have to download the, possibly large, resource
    4. Andrew WoodsEsmé CowlesSimeon Warner - agree that we should relax support for API creation of external content to SHOULD
    5. ACTION - Andrew Woods to update PR242 with the change to SHOULD above, and other changes for "if supported"
  4. Versioning issues
    1. "Prohibit PATCH on LDPCv"
      1. https://github.com/fcrepo/fcrepo-specification/pull/244
      2. Agree to merge as 3 +1, no -1, 3 days old (needs minor syntax fix)
    2. Propose the addition of new terms to the LDP namespace

      1. https://github.com/fcrepo/fcrepo-specification/issues/245
      2. Agreement that this is not critical for milestone
    3. Clarify reliable method to write into LDPCv

      1. https://github.com/fcrepo/fcrepo-specification/issues/250
      2. Agreement that change wording to except LDPCv, while retaining MUST
      3. ACTION - Simeon Warner to make PR for https://github.com/fcrepo/fcrepo-specification/issues/250
    4. Include `Vary` header in LDPRv `OPTIONS` response

      1. https://github.com/fcrepo/fcrepo-specification/issues/246
      2. Agree to do one of these 
      3. ACTION - Andrew Woods to make PR for https://github.com/fcrepo/fcrepo-specification/issues/246
    5. Added text for HEAD and GET requests to LDPCv objects - related to #244
    6. What are the semantics of version restoration?
      1. https://github.com/fcrepo/fcrepo-specification/issues/238
      2. Consensus: drop version restoration and use ingest-by-reference instead
      3. skipped, push forward
  5. Misc PRs and Issues

    1. Adding section clarifying acl:Append - pending review from Benjamin Armintor and Daniel Lamb - merged
    2. Add section on ACL linking on resource creation - pending review from Benjamin Armintor
      1. https://github.com/fcrepo/fcrepo-specification/pull/214
      2. https://github.com/fcrepo/fcrepo-specification/issues/176
      3. skipped, push forward
    3. Torching Depth header in lieu of advertising recursive DELETEs
      1. https://github.com/fcrepo/fcrepo-specification/pull/241
      2. https://github.com/fcrepo/fcrepo-specification/issues/234
      3. skipped, push forward
    4. Use Location header for ingest-by-reference
      1. https://github.com/fcrepo/fcrepo-specification/issues/236
      2. Perhaps needs more discussion and thought. There are two key use cases we imagine: 1) ingest of binary, 2) restore of version.
      3. ACTION - all to review and comment on https://github.com/fcrepo/fcrepo-specification/issues/236
  6. Countdown to RC...
    1. Esmé Cowles expects to be able to make next calls
    2. Andrew Woods and Simeon Warner at Samvera Connect next week, will try to do call
    3. Andrew Woods at retreat following week, will not be able to make call
    4. Try to wrap up with work on 22 Nov, if necessary do extra work on 27 Nov (these days work for Andrew WoodsEsmé CowlesSimeon Warner). Will also need to work out exactly what it means to make the RC and push it out

Action Items

  • No labels