Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
• International toll free:  http://www.readytalk.com/intl 
  
  • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
  • Once on the call, enter participant code 2257295
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• A. Soroka 
• Unknown User (acoburn)
• Michael Durbin
• Jared Whiklo 
• Yinlin Chen 
• Andrew Woods
• Osman Din 
• David Wilcox
• Stefano Cossu
• Jon Roby
• Unknown User (escowles@ucsd.edu)
• Unknown User (daniel-dgi)
• Doron Shalvi

Agenda

1. Islandora / F4 migration update
2. LDP "Link: constrainedBy" 
3. Open Repositories committer meeting planning

4. From last week: High-priority issues

   Audit issues: fixity  internal/external URIs  LDP etags  response subjects  post/patch constrained-by  put to fail if triples not persisted  collapse binary and description properties  create point-like objects  disallow put/patch with RDF that includes other subjects  Performance GC error  blank node map  Clean up remove UUID from default transform  remove UUID from responses  remove Blanknode from ontology  403 when updating pairtree resources  update mechanism for client-provided checksums  UI Enable creation of container with text/turtle body

5. Tickets resolved this week:

6. Tickets created this week:

7. ...

Minutes

11.05

• Greetings

11.05 - 11.10 (1)

• Andrew: Close to initial round of upgration pilots. Any comments?
• Mike/Danny: Not much activity, perhaps later this week (work on a ticket or two).
• David pilot standing: Talking to Carol about drafting a message that summarizes where we are with the pilots. Expect a message next week message about pilot outcomes. Some info already in the wiki (from Columbia, etc). Pilots are at various stages. National Library of Wales ran into a (few) issue(s) (GC issue) and Glen looked at it.
• Andrew to Mike: The Javadoc issue should be resolved now. In 4.1.1, one dependency got bumped up that broke the Javadoc.

11.10 (2)

• Some IRC activity this morning regarding "Link: constrainedBy".
• Jared: LDP compliance failing a test because of data header. 
• FCPREO-1418 lists many solution approaches.
• Andrew: In LDP specification http://www.w3.org/TR/ldp/#ldpr-gen-pubclireqs, it states if a server does not allow a POST or PATCH to succeed, in the response there must be a constrainedBy header. 
• ajs6f: Note the spec mentions: "and a target URI identifying a set of constraints". 
• Andrew mentions community approaches, e.g., having static page on why some request failed. Little bit of ambiguity, but there are some success stories.
• ajs6f: Preferable to have dereferencable mechanism. How precise and machine-actionable it can be made is a question, but things can be made better. It could be a "human" thing, e.g., "your RDF is junk!". We do have MalformedRdfException, so there could be similar exceptions that have messages like 'your request contains a subject not part of the resource'. Alternatively (to static pages), a dereferenceable link. May be very had to make things actionable. But definite improvement to ergonomics.
• Esme: RDF is not only human readable but machine actionable
• Andrew: So. . . Feelings one way or the other?
• Esme advocating for external ontology like approach. "Seems easiest to me". Network access issue would be better handled, etc. 
• Andrew: Having static pages deployed with Fedora seems a bit tighter.
• ajs6f: My use case is while travelling, if I'm disconnected, things should still function. But not a strong enough use case. In some ways, having a coherent artifact is "kind of nice".

11.35 (3)

• Andrew: Meeting is for the general tech community (not just committers). Please add/remove names and agenda to the page.
• Two specifc topics that recently came up: (a) ? (b) Proposal from Data Conservancy. DC has some use case that in F3 terms would be considered a disseminator. Design focus on using Camel and addressing various dissemeniatior like scenarios and possibly having JAX-RS drop in modules (i.e., not part of core code base). 

11.45 (4, 5, 6)

• Andrew: For the LDP section are there tickets that folks will be working on (soon)? (Silence.)
• Andrew: Garbage collection issue faced by the National Library of Wales. Might be addressed by the work that Mike is doing. So, it might get tackled in another way (tool) but Andrew suspect there might be still an issue lurking (Jon might be able to take a look at in the sprint).
• FCREPO-1411: Might already be addressed and is related to the work Jared is doing for the other constraints. Jared to look at 1411 - 1442 to see if that's not the case.
• Clean up tickets: Yinlin is working on a, b, c. Esme to continue work.