Versions Compared

Old Version 10

changes.mady.by.user Daniel Lamb

Saved on

compared with

New Version 11

changes.mady.by.user Simeon Warner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Reviewing charter/timeline

  2. From Tuesday's Memento call

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

      1. http://fedora.info/2017/06/30/spec/#general-1

    2. Memento validator

  3. PRs

    1. Added text for HEAD and GET requests to LDPCv objects
    2. Add to definition of LDPRv that not only URI-R but also TimeGate
    3. Add missing anchors and move some from h2 to section tag
    4. Add section on ACL linking on resource creation
    5. Add note about non-constraint of RDF data storage model
    6. Adding language for remote ACL and Group Listing resources
    7. Adding section clarifying acl:Append
    8. Creating versions with POST
      1. https://github.com/fcrepo/fcrepo-specification/issues/215
      2. https://github.com/fcrepo/fcrepo-specification/pull/239
  4. Issues
    1. Use Location header for ingest-by-reference
      1. https://github.com/fcrepo/fcrepo-specification/issues/236
      2. Looks good, needs a PR
    2. Require support for external content with access-type=URL
      1. https://github.com/fcrepo/fcrepo-specification/issues/237
      2. Looks good, needs a PR
    3. What are the semantics of version restoration?
      1. https://github.com/fcrepo/fcrepo-specification/issues/238
      2. To drop specifying restoration?
    4. Modeshape Impl: Interaction models effectively can't be changed
      1. https://github.com/fcrepo/fcrepo-specification/issues/229
      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 

        1. https://github.com/fcrepo/fcrepo-specification/issues/234

        2. Use OPTIONS to signal availability of DELETE

        3. Agreement? Awaiting PR

      2. 3.8 External Binary Content 

        1. https://fcrepo.github.io/fcrepo-specification/#external-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. https://github.com/fcrepo/fcrepo-specification/issues/211: Clarify response when copying remote content
    3. 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
  7. Authorization issues
    1. issue-165: Removing support for acl:accessToClass?
      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
            1. explain what accessToClass does
            2. inference is a MAY 
    2. issue-172: Clarify algorithm for finding authorizations
      1. Still pending clarification from Solid


Notes

  • Memento 
    • Andrews notes good discussions between then implementation teams and the Memento team. The Memento folks raised question of why we chose URI-R == URI-G. Those on call feel that this is a good choice that avoids creation of another dangling resource so, in our context, it saves effort without introducing any problems. There isn't any suggestion to do something else, or any known problems with doing URI-R == URI-G
    • Fedora modeshape implementation will likely move from 200 to memento through timegate to a redirect pattern
  • Compliance test suites
    • Colin Brittle is implementing a Python test suite
    • Java test suite development has focused on section 3 (LDP-CRUD perhaps 3.3–3.7). Work is based on the LDP test suite and so generates HTML and EARL output. Some extra work to do to refine the EARL
  • Timeline
    • Try to get out a release out by Thanksgiving
    • Getting lots of good feedback/questions from folks doing implementation work

Action Items

  •