Page History

...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-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

1. Discussion of handling external-content
   • See: https://github.com/fcrepo/fcrepo-specification/issues/338

Regarding 2.a. :

• Two options:

  • Reduce the granularity of our label  

  • Modify Memento spec

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

escowles:

409 Conflict seems reasonable to me

...

• Consensus on option 1.
  • Return 409 when timestamps conflict.
• Agreement that server-managed or distributed backends could have trouble with that

...

Bethany Seeger & awoods:

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

...

• 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]

...

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.

& 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.

It looks great on the current proposal in 3.aConsensus 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