<gkellogg>
Not repetative, as hashes may be the same, but values not. But, if they’re different, checking hashes first is an earlier exit.
<tjohnson>
gkellogg++ learned something today :)
<tjohnson>
Starting the core group meeting
<tjohnson>
gkellogg says: from now on, let's scribe meeting in something like the w3c way
<tjohnson>
* gkellogg: 1.99 hit a couple of glitches along the way; but is coming along
<tjohnson>
* gkellogg: we need to sort out handling for 1.99, deprecations, and 2.0 behavior
<tjohnson>
* gkellogg: what is the status around that with transactions?
<tjohnson>
* bendiken: semantics change, we'd have to play fast and loose
<tjohnson>
* bendiken: pulled latest changes to 1.1.x "transactions" into changesets; we could backport changesets and deprecate. it may be difficult to detect the use of changesets as transactions
<tjohnson>
* bendiken: consider a 'from future import *' approach
<gkellogg>
tjohnson: how substantial are the changes to Repository?
<tjohnson>
* bendiken: the bulk of the changes are in RDF::Repository. notion is that Repository needs to support transaction; operating on reified state of the repository.
<tjohnson>
* gkellogg: repository implementations that are maintained: RDF::DO, RDF::Mongo, and RDF::AggregateRepo.
<tjohnson>
* gkellogg: let's target transaction changes for 1.99.1, using the future pattern
<tjohnson>
resolved: target transaction changes for 1.99.1, using the future pattern
<tjohnson>
topic: broken links in rubyforge
<tjohnson>
* bendiken: found login; will redirect to ruby-rdf.github.io as appropriate
<tjohnson>
* gkellogg: we talked about the Dataset/Repository split at some point in the past; Dataset could be just a read-only repository. Loading into Repository require's Writable#load and Mutable#insert.
<tjohnson>
* bendiken: could you populate on instantiation?
<tjohnson>
* bendiken: could make the Dataset immutable after the `#new`
<tjohnson>
* bendiken: Repository would be a higher level concept; what's the reason we wanted to make this split?
<tjohnson>
* gkellogg: it's just conceptual. Dataset is an RDF concept, but Repository is not.
<tjohnson>
proposal: add Dataset as a new mixin that includes Queryable; that should suit as a first cut.
<tjohnson>
* bendiken: we need to include that via Future, since Dataset is already aliased to Repository
<tjohnson>
resolved: Dataset as described above targeted for 1.99.1; included via Future
<gkellogg>
tjohnson: still in progress, focused on nailing down the Raptor side; there are a couple of issues that jcoyne opened #227 which is related.
<gkellogg>
… I’m trying to figure out what the changes are. The Turtle changes look good. The other readers need to be updated too.
<tjohnson>
* gkellogg: will take a look at RDFa, Trig, Trix, and some of the older
<tjohnson>
* tjohnson: I will spec out the minimal interface
<tjohnson>
* bendiken: how are we logging the errors?
<tjohnson>
* gkellogg: capturing an Array of Strings errors
<tjohnson>
* tjohnson: will submit a PR for `rdf-spec`; that PR will probably not require changes for RDF::Turtle, we can discuss further on the PR
<gkellogg>
tjohnson: The original change is pretty significant for performance on inserts to Repositories/Graphs. After I opened this, it become less important due to Transactions.
<gkellogg>
… But, support for this is important.
<gkellogg>
… rdf-blazegraph makes this automatic and will work well.
<tjohnson>
* gkellogg: target this for 1.99.1 ?
<tjohnson>
* tjohnson +1. I will submit a revised PR
<gkellogg>
tjohnson: I think the desired behavior is, if I have an N-Triples reader loaded, which support for content_type and symbol access, and I now require no-repy:special-rdf-ntripes; at that point, I expect my implementation to take predicdence.
<tjohnson>
* gkellogg: reader `#for` support may not overlap
<tjohnson>
proposal: keep the officially supported `#for` format support uniform where possible
<tjohnson>
* gkellogg: might be good to handle cases like non-compliant readers
<tjohnson>
* bendiken: could add quality value; but favor simply using last loaded
<tjohnson>
* tjohnson: will that work for n-triples? `require 'rdf'; require 'rdf/raptor'; require 'rdf/ntriples'` works?
<tjohnson>
* bendiken: yes, but potentially complicated by internal use
<tjohnson>
resolved: enforce last loaded target for 1.99.1