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
- Jared Whiklo
- Yinlin Chen
- Andrew Woods
- Joshua Westgard
- Nick Ruest
- Aaron Birkland
- Daniel Lamb
- Danny Bernstein
- Unknown User (acoburn)
- Longshou Situ
- Kieran Etienne
- Jim Coble
- Simeon Warner (phone only)
Agenda
Implications of blank node redesign:
- Based on community input 4.7.3 is reasonable
- Need upgrade utility:
Potential 4.7.3 release
- Benjamin Armintor: Input re:external-content from LDCX
- ...
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
### Kefo's Issue on the List
Traversing the repository looking for corrupted resources won't work because the ldp:contains predicate is not set for the corrupted resource.
500's were received during the long-running ingest which led to this discovery.
Possibly a concurrency issue, which could be eliminated as a cause if there was more information available.
Unfortunately no TRACE level logging available, nor stack traces from the logs for a root cause.
Would be good to see if it's possible to do an import/export at the ModeShape layer to see if ModeShape can read the corrupt resources.
Mike Durbin thinks it is possible to provide a patched Fedora to ameliorate the issue if we can isolate where the issue is occurring.
### Possible release for skolemizing blank nodes
All resolved issues resolved in the master branch are non-breaking and could be rolled into a minor release.
Although not strictly required, those with existing blank nodes that plan on ingesting new ones, you'd have both hash uris and .well-knowns.
Tenative +1 to get those changes out and go through the process of community testing.
The new Jena library changes some xsd info that could cause some existing clients to break without a small configuration change.
Simeon suggested using configuration to enable new blank node behavior, but to leave it disable by default. Then it's DEFINITELY non-breaking, as opposed to posibly non-breaking.