...

• Longshou Situ
• Unknown User (acoburn)
• Esmé Cowles
• Yinlin Chen 
• David Wilcox
• Nick Ruest 
• Benjamin Armintor
• Bethany Seeger
• James R. Griffin III
• Aaron Birkland
• Jared Whiklo 
• Jack Hill 
• Michael Durbin
• Andy Wagner
• Jim Coble
• Andrew Woods
• Jennifer Lindner
• Daniel Lamb
• Doron Shalvi

Agenda

1. Still time to participate in the Fedora Value Proposition brainstorming
2. Concurrency control options with lack of strong ETags
   
   1. If-ModifiedUnmodified-Since has only second precision
   2. Use cases would be nice to determine common need
3. Import/Export pre-planning
4. Linked Data Notifications

5. Status of "in-flight" tickets

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

1. Still time to participate in the Fedora Value Proposition brainstorming
   • The Fedora Value Proposition brainstorming exercise will close within the week.  Please take a look and add your comments.

2. Concurrency control options with lack of strong ETags

   • Background discussion: Strong ETags are desired, but RDF doesn't allow us to make those guarantees. We had planned to use If-Unmodified-Since: headers, but those have limited granularity of one second. At least one site has a use case for a better solution. Jim Coble said that Duke might depending on the direction that Hydra goes.

   • LDP standards are heading towards using If-Unmodified-Since: . We may still need to make better guarantees in Fedora.

   • There were several proposals about how to deal with this issue:

     • Use a local header (e.g. X-If-Weak-Match:) with weak ETag contents but different semantics

     • Use higher precision dates in If-Unmodified-Since. HTTP/1.1 forbids using a different time format.

     • Solve the problem in clients by having them modify their behavior to strip out the weak identifier.

       • There was discussion of how stable this option will be. It will work for now, but might break in the future.

       • ETags allow this behaviour since only the ID is opaque, not the weakness indicator.

     • Use properly formatted If-Unmodified-Since:, but don't have the timestamps reflect actual time, but instead mapped from a better counter.

       • Clients need to know that they can rely on this, but would not require special processing of the header on the clients.

       • Fedora would need additional work to generate the header. The amount of work required is unknown.

     • (also mentioned on IRC) HEAD requests could return strong ETags. Clients most often send HEAD requests first. It may not be allowed for HEAD requests to return different headers.

   • n.b. All of the proposed solutions require clients to be aware of the Fedora specific behavior.

   • Conclusion:

     • The LDP spec will change to support the use of If-Unmodified-Since:. For use cases where that is not good enough, clients can treat weak ETags as strong.

     • Other options should continue to be explored as needed.

     • We would like the improve how ETags are generated

       • Danny will open a ticket about this.

3. Import/Export Sprint Nick Ruest

   • Starts at 11:00 EDT, Monday, August 29th.

   • In the first meeting we will talk about Phase one items and assign tasks.

   • A wiki page for the sprint meeting will be created under the Misc. Meeting section of the wiki.

   • The minimal goals for the sprint are the Phase one requirements.

   • The fedora-tech list will be included in discussions, so that those who are not participating in the sprint, but would like to stay abreast

4. Linked Data Notification

   • Amherst is interested

   • There is a W3C draft standard

   • Fedora currently has various ways to do auditing (e.g. built in audit functionality, sending events to an external triple store, storing events as object in the repository).

   • LDN complements what already exists in Fedora by standardizing an endpoint for seeing notifications.

   • Is there interest from Fedora?

   • Conclusion:

     • This is in line with LDP and what we are doing. Please review the spec and we will talk more next week.

5. In-flight tickets

   • FCREPO-2120 Bethany Seeger will review and close ticket

   • FCREPO-2111 and FCREPO-2112 Benjamin Armintor would like for someone to take over. There were no volunteers.

   • FCREPO-2055 Trying to replicate at modeshape level.

   • FCREPO-2031 Needs re-review

   • FCREPO-2028 Jared Whiklo has it on TODO list, and should have some time next week. It is mostly maven work.