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
...
Tickets resolved this week:
Tickets created this week:
- ...
Minutes
- Open Repositories committer meeting reflections
- fcr:metadata and NonRDFSource descriptions
- API extension framework to provide a Fedora 4 equivalent to disseminators or other kinds of functionality, independent of the core Fedora 4 codebase
- How do we align our REST API with standards, partitioning the API, adding test compatibility kits, etc.
- Improving codebase by taking advantage of Java 8, reducing dependency sprawl, OSGI-ifying Fedora
- Some dependency conflicts with the Servlet API version that complicate supporting Karaf and Tomcat 7
- 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
fcr:metadata and NonRdfSource descriptions
- There are limitations to the NonRDFSource descriptions (fcr:metadata): can't use blank nodes or hash URIs, child nodes or child NonRDFSources
- 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
- The other use case is NonRDFSources that describe other NonRDFSources (e.g., FITS that describes a TIFF)
- This could be accomplished by creating child NonRDFSources, or making fcr:metadata a container, or allowing linking to a separate container
- Option 2 is to make fcr:metadata a container, which would allow changes
- General agreement that NonRDFSource descriptions should have a single subject and it should be the binary
- 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.
- A different approach would be to allow creating different kinds of deletion policies:
- Delete the link
- Delete the linked resource
- Return an error
- Supporting these different kinds of policies would be a Fedora-ism, but in support of LDP – maybe an extension.
Action: Esme will create two tickets:
- fcr:metadata should be a container
- fcr:metadata should have a single subject (the NonRDFSource URI) – this may exist
4.2.1 Release manager?
- Good to have periodic releases, and even better to get more people involved in the release process
- Nick volunteered to be the release manager for 4.2.1.