Versions Compared

Key

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

...

Agenda

  1. Welcome to new Fedora Committer: Yinlin Chen
  2. Alignment Sprint 1 Progress ReportReport  https://jira.duraspace.org/issues/?filter=14401
    1. Memento-Datetime header granularity issue RFC-1123
      1. The memento spec does not support version sub-second granularity 
      2. There is no problem with us supporting it internally (when creating mementos without specifying the header).
      3. However is we support sub-second granularity it is not clear how we will be able to import versions without losing information.
      5.7.3 LDP-NR - Patching Binaries (LDP-NR) - do we plan to support?
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2710
    3. Challenges with acl:Append
      1. https://fcrepo.github.io/fcrepo-specification/#append-ldprs
      2. The spec defines rules at the HTTP method layer while the ACLs are implemented in the jcr layer.
      3. It makes it difficult to determine whether a POST, PUT or PATCH has occurred and whether a node existed when the transaction began.
      4. The javax.jcr.Node interface uses the same permsission (org.modeshape.jcr.SET_PROPERTY) for adding, updating and removing properties and generates the same: 
      5. reference tickets: 
        1. Jira
          serverDuraSpace JIRA
          columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2715
        2. Jira
          serverDuraSpace JIRA
          columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2716
        3. Jira
          serverDuraSpace JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO
      -2710
        1. -2717



    4. 5.7.3 LDP-NR - Patching Binaries (LDP-NR) - do we plan to support?

  3. Specification of External Content interaction

    1. Code Block
      :Request:
      Link: <some-URI>;
               rel="http://fedora.info/definitions/fcrepo#ExternalContent";
               type="image/jpeg";
               handling=<copy|redirect|proxy>
      
      :Response:
      Content-Location: <some-URI>
      Content-Type: image/jpeg
      
      :Fedora advertising support:
      OPTIONS
      Accept-External-Content-Handling: <copy|redirect|proxy>
      
      :Comma separated list like Accept, if supporting multiple handling approaches:
    Challenges with acl:Append
    1. https
      :
      //fcrepo.github.io/fcrepo-specification/#append-ldprs
    2. The spec defines rules at the HTTP method layer while the ACLs are implemented in the jcr layer.
    3. It makes it difficult to determine whether a POST, PUT or PATCH has occurred and whether a node existed when the transaction began.
    4. The javax.jcr.Node interface uses the same method call (setProperty() for adding, updating and removing properties. 

  4. Feedback on Peter Eichman's writeup on the use of userAgent and groupAgent base URI's and their relationship to WebAC in order to clarify whether or not what if anything needs improvement/clarification/alignment?

Sprint tickets 

Jira
serverDuraSpace JIRA
jqlQueryfilter=14401
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

Ticket Summaries

  1. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Minutes

Separate tickets

  1. Creating Mementos when not providing Memento-Datetime
    • no body
  2. Converting dynamic properties to static properties

Other

  1. ACTION: BenP to submit an initial, minimal PR for creating no-body LDPRv's

Updates from spec editors meeting

...

Regarding 2.a:

Bethany Seeger & awoods:

Memento Tools - Validator: http://mementoweb.org/tools/validator/


Regarding 2c:  Consensus seems to be that we should plan to that pull the webac out of the modeshape layer and handle it at the http layer.  That would both solve the problem with supporting acl:Append and reduce our dependency on modeshape paving the way for swapping it with something else.

Regarding 3. external content pr

...

: https://github.com/fcrepo/fcrepo-specification/

...

pull/343

Use POST/PUT requests to create external content nodes.

Consensus on proposed API changes. 

Action Items

  •  Danny Bernstein determine whether there is any case where a PUT on a TimeMap would make sense. If there is it should be raised with the specification editors.
  •  Peter Eichman to do a short writeup on the use of userAgent and groupAgent base URI's and their relationship to WebAC in order to clarify whether or not what if anything needs improvement/clarification/alignment. ACL Agents - Strings vs. URIs