...
Wanted to check with Tamsin on where things are with RDF upgrade.
Concern that I have is that Greg Kallick(?) has a PR into LDP or to 3.2 for all RDF gems
In Avalon-space we're stuck in an older rdf-vocab space as some things have changed
Might drop rdf-vocab long term
Tamsin
What happened over holidays - Greg rewrote in-memory data repository
Past version used a Hash Arraymapped Tree to make small memory footprint while allowing for fast updates and fully-snapshottable transactions
Grab data in memory at any point and just hold it in memory
Downside: data structure was fundamentally unordered - find for RDF but not everything else.
Greg flipped it back - not sure motivation
New implementation that looks a lot like an old implementation
Snapshotting is retained
Some breakages as a part of that - some naming changed. On Monday Tamsin renamed to the previous name. Should be fixed.
However, a little worried about the memory properties of this datastructure
If being conservative, might not want to upgrade RDF to latest yet - especially where people are doing big reindexes, this might have issues
Going to do some benchmarking/testing - we might want to revert if it doesn't hold up
Greg concerned about breaking RDP/active-triples, think these changes are related to that
Chris put some comments but not much in the PR review
Seems like upgrade to 3.2 forced all other RDF gems to 3.2 , concerned about that
Tamsin - we may be able to change that. Will look at it this afternoon.
Moderator/notetaker next week
Moderator: Max Kadel
Notetaker: Chirs Colvard
Lynette will solicit feedback for Questioning Authority PR - Chris Colvard offered to stay on Zoom and talk about it