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)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• 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 

• Longshou Situ
• Unknown User (acoburn)
• Esmé Cowles
• Yinlin Chen 
• Nick Ruest 
• Bethany Seeger
• Aaron Birkland
• Jared Whiklo 
• Jim Coble 
• Andy Wagner 
• Andrew Woods
• A. Soroka
• Jennifer Lindner
• Andy Wagner  
• Michael Durbin
• Marcus Barnes
• Jack Hill
• Jenn Colt

Agenda

1. Should we move information in system-managed triples into HTTP headers?
2. gradle in fcrepo-exts? 
3. Should we remove the ability to delete tombstones?  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. 2016 - 2017 Technical Priorities
5. 4.7.0 release plan

   1. Fedora Release Process 

   2. Policy - Release Candidates

   3. https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1283770870 

6. Specification Sprint - which and when
7. PennState Import/Export sprint planning
   1. Priorities
   2. BagIt implementation design
   3. Remote participation possibilities
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
8. ...

9. Status of "in-flight" tickets

   Click here to expand...

   

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   

2. Tickets resolved this week:

   Click here to expand...

   

3. Tickets created this week:

   Click here to expand...

   

Minutes

• Should we move server-managed-triples into HTTP headers?
  • Unknown User (acoburn) expressed concern that they must also appear in triples to facilitate indexing and so forth
  • Esmé Cowles brought up the example of rdf:type being important
  • The LDP spec may require rdf:type to show up in the triples, but the fedora-namespaced triples we can do what we want to with
  • It's also unclear what standard headers we could use... especially for literals, which can't be the subject of link headers.
  • Andrew Woods and Unknown User (acoburn) indicated that we should do an inventory of our server-managed triples, and we should consider cleaning up the ontology. (like number of children)