Page tree
Skip to end of metadata
Go to start of metadata



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


  1. Reviewing charter/timeline

  2. From Tuesday's Memento call

    1. Why was it decided to have URI==URI-G?


    2. Memento validator

  3. PRs

    1. Added text for HEAD and GET requests to LDPCv objects - pending response from Ben Pennell
    2. Add section on ACL linking on resource creation - pending review from Benjamin Armintor
    3. Add note about non-constraint of RDF data storage model - pending review from Benjamin Armintor
    4. Adding language for remote ACL and Group Listing resources - pending review from Benjamin Armintor
    5. Adding section clarifying acl:Append - pending review from Benjamin Armintor and Daniel Lamb
    6. Creating versions with POST - pending response to review
    7. Prohibit PATCH on LDPCv - pending review from ALL
  4. Issues
    1. Use Location header for ingest-by-reference
      2. Looks good, needs a PR
    2. (tick) Require support for external content with access-type=URL
      2. pr-242
    3. What are the semantics of version restoration?
      2. To drop specifying restoration?
    4. Modeshape Impl: Interaction models effectively can't be changed
      2. Nothing to be done for the ModeShape impl... others will be different
  5. Revisit strictness of requirements for external content, recursive deletion, client-specified ACLs, etc.
    1. Specifically:
      1. 3.7.1 Depth Header 


        2. Use OPTIONS to signal availability of DELETE

        3. Agreement? Awaiting PR
      2. 3.8 External Binary Content 


        2. Support for 'message/external-body'

  6. External content issues:
    1. Need to separate proxy vs. ingest-by-reference operations
      1. Content-Location cannot be used to indicate the URL should be used instead of the request body
    2. Clarify response when copying remote content
    3. 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
  7. Authorization issues
    1. issue-165: Removing support for acl:accessToClass?
      1. Wait on response to
      2. CLAW only uses ACLs for very basic partitioning of drupal instances
        1. Suggestion, add wording that indicates:
          1. implementations MUST do accessToClass
            1. explain what accessToClass does
            2. inference is a MAY 
    2. issue-172: Clarify algorithm for finding authorizations
      1. Still pending clarification from Solid


Action Items

  • No labels