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
• Osman Din 
• David Wilcox 
• Unknown User (escowles@ucsd.edu) 
• James R. Griffin III 
• Nick Ruest 
• Jared Whiklo
• Benjamin Armintor
• Harshakumar Ummerpillai

Agenda

1. ...

2. Tickets resolved this week:

   Click here to expand...

   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:

   Click here to expand...

   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.

4. ...

Minutes

1. Open Repositories committer meeting reflections
   
   1. fcr:metadata and NonRDFSource descriptions
   2. API extension framework to provide a Fedora 4 equivalent to disseminators or other kinds of functionality, independent of the core Fedora 4 codebase
   3. How do we align our REST API with standards, partitioning the API, adding test compatibility kits, etc.
   4. Improving codebase by taking advantage of Java 8, reducing dependency sprawl, OSGI-ifying Fedora
      1. Some dependency conflicts with the Servlet API version that complicate supporting Karaf and Tomcat 7
      2. High-level benefits of OSGI are being able to add and remove modules at runtime, and not need the webapp-plus project to pre-compose different options

2. fcr:metadata and NonRdfSource descriptions

   1. There are limitations to the NonRDFSource descriptions (fcr:metadata): can't use blank nodes or hash URIs, child nodes or child NonRDFSources
   2. We can add some of that functionality to fcr:metadata, e.g. blank nodes and hash URI support – this seems uncontroversial and we can probably just file a ticket
   3. The other use case is NonRDFSources that describe other NonRDFSources (e.g., FITS that describes a TIFF)
      1. This could be accomplished by creating child NonRDFSources, or making fcr:metadata a container, or allowing linking to a separate container
   4. Option 2 is to make fcr:metadata a container, which would allow changes
   5. General agreement that NonRDFSource descriptions should have a single subject and it should be the binary
      1. Some uneasiness about the subject, but having it be a single-subject description will make it easier to change if we look at how other LDP implementations handle this.
   6. A different approach would be to allow creating different kinds of deletion policies:
      1. Delete the link
      2. Delete the linked resource
      3. Return an error
   7. Supporting these different kinds of policies would be a Fedora-ism, but in support of LDP – maybe an extension.

   8. Action: Esme will create two tickets:

      1. fcr:metadata should be a container
      2. fcr:metadata should have a single subject (the NonRDFSource URI) – this may exist

3. 4.2.1 Release manager?

   1. Good to have periodic releases, and even better to get more people involved in the release process
   2. Nick volunteered to be the release manager for 4.2.1.