...

• Benjamin Armintor
• Esmé Cowles 
• Daniel Lamb 
• Simeon Warner
• Andrew Woods

Agenda

...

1. External content issues:
   1. https://github.com/fcrepo/fcrepo-specification/issues/211: Clarify response when copying remote content
   2. https://github.com/fcrepo/fcrepo-specification/issues/210: Clarify "expires" parameter
      1. Suggestions:
         1. Potentially remove the "expiration" header parameter
         2. Add "Content-Location" under PUT for ingest by reference
            
            1. If you wanted to add to repo, you would retrieve and upload
         3. Further discussion with Benjamin Armintor before taking action
2. Versioning issues:
   1. https://github.com/fcrepo/fcrepo-specification/issues?q=is%3Aissue+is%3Aopen+label%3Atopic-versioning
   2. Other versioning questions from API Alignment sprint: Versioning/Authorization Design
3. Revisit strictness of requirements for external content, recursive deletion, client-specified ACLs, etc.
   1. Specifically:

      1. 3.7.1 Depth Header 

         1. https://fcrepo.github.iocom/fcrepo/fcrepo-specification/#httpDELETEDepthissues/234

         2. Use OPTIONS to signal availability of DELETECould possibly be removed entirely with an informative note (re: WebDAV) and expectations about OPTIONS when recursive not supported

      2. 3.8 External Binary Content 

         1. https://fcrepo.github.io/fcrepo-specification/#external-content

         2. Support for 'message/external-body'

   External content issues:

   2. https://github.com/fcrepo/fcrepo-specification/issues/211: Clarify response when copying remote content
4. Notifications section:
   1. Esmé and Danny to review and create issues
   2. Passing mention of LDN - can it be removed? Probably not.
   Barring further feedback from Esmé, good Good enough for candidate impls? 
5. Fixity section:
   
   1. Simeon Warner thinks this is done. , see review in 2017-09-14 - API Spec Meeting notes. Issue 218 was created and has been fixed, issue 235 is about naming of digests in modeshape implementation, not about spec. No other issues.

...

2. Authorization issues
   1. issue-165: Removing support for acl:accessToClass?

1. 1. 1. Wait on response to https://github.com/solid/web-access-control-spec/issues/22
      2. CLAW only uses ACLs for very basic partitioning of drupal instances
         1. Suggestion, add wording that indicates:
            1. implementations MUST do accessToClass
            2. explain what accessToClass does
            3. inference is a MAY 
   2. issue-168: Cross-domain Authorization?
      
      1. PR: https://github.com/fcrepo/fcrepo-specification/pull/208 — needs
review from Andrew, Ben, Simeon
2. 1. 1. to resolve conflicts
   2. issue-170: Require acl:Append and acl:Control
      1. PR: https://github.com/fcrepo/fcrepo-specification/pull/206 — needs review from Andrew, Ben
   3. issue-172: Clarify algorithm for finding authorizations
      1. Still pending clarification from Solid
   4. issue-176: ACL creation and linking -- be explicitly silent or specify?
      1. PR: https://github.com/fcrepo/fcrepo-specification/pull/214 — needs review from Andrew, Ben, Danny
Versioning issues:
4. https://github.com/fcrepo/fcrepo-specification/issues/215 — clarifying creation of versions with PUT
5. Other versioning questions from API Alignment sprint: Versioning/Authorization Design
6. External content issues:
   1. https://github.com/fcrepo/fcrepo-specification/issues/210: Clarify "expires" parameter
      1. Suggestions:
         1. Potentially remove the "expiration" header parameter
         2. Add "Content-Location" under PUT for ingest by reference
            
            1. If you wanted to add to repo, you would retrieve and upload
         3. Further discussion with Benjamin Armintor before taking action

Notes

1. Do we want to require specific values for Depth header or external-content access-type values?
   1. Depth: unless we can agree on at least one value to require support for, we should leave this alone
      1. Is there a response header to advertise which Depth values are supported?
      2. Alternative: Deletes are always recursive, if you can't do recursive deletes, then don't include DELETE in an OPTIONS response
         1. ACTION: Benjamin Armintor will open a PR
   2. User-supplied ACLs: lots of different options for implementation, maybe better to leave this alone
   3. External content: 
      1. Require access-type="URL"?
         1. ACTION: Esmé Cowles will open an issue for requring access-type="URL"

Action Items

...

...

•  

...