You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees

Agenda

  1. Welcome to new Fedora Committer: Yinlin Chen
  2. Alignment Sprint 1 Progress Report  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.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.


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

  3. Specification of External Content interaction
    1. :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:
  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 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

  1. Discussion of handling external-content

2.a.

Two options

  1. Reduce the granularity of our label  

  2. Modify Memento spec


Change the current implementation to not have label in microsecond but just second.

escowles:

409 Conflict seems reasonable to me

agree that server-managed or distributed backends could have trouble with that

Bethany Seeger & awoods:

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

whikloj:

https://jira.duraspace.org/browse/FCREPO-2727 & https://jira.duraspace.org/browse/FCREPO-2728

2.c.

Change the Fedora spec. Change to May instead of a Must. [Spec 5.7.1]

whikloj: Section 5: "To configure access control restrictions, implementations MUST follow the recommendations of Web Access Control [SOLIDWEBAC] with the following additional requirements:"

Bethany Seeger: Can you read this the above this way “If you choose to configure access control restrictions, you MUST follow Solid Webac”? (edited)

awoods:https://fcrepo.github.io/fcrepo-specification/#append-ldprs

Modeshape doesn’t give delete and add property permission, only set property. This problem is because authz is being enforced at the Modeshape layer, and one logical API operation translates into multiple modeshape operations.

Option 1: using injection. like injecting it in the RDF diffing code, so you could e.g., look for deleting triples and throw an exception if the user only had append permission. But could break the design also need to think about performance impact @whikloj.

@Peter Eichman suggests moving the ACL check out of Modeshape and into the HTTP layer  or at the very least outside of modeshape.

Find a feasible way to get out from underneath Modeshape the webac code has lots of jcr in it.

3. external content pr: https://github.com/fcrepo/fcrepo-specification/pull/343

Use POST/PUT requests to create external content nodes.

It looks great on the current proposal in 3.a

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
  • No labels