Gregg Kellogg

I think this basically comes down to the theory of execution of the SPARQL operators, which is inherently bottom-up, meaning that this bottom level `(path *rdf:rest)` is executed to create...

Some more thoughts on what could eventually happen: 1. Queries ultimately come down to a series of BGPs, which are handled using `rdf::Query#execute`. Although unused, this accepts solution bindings. In...

Generating the query form from the algebra is a bit experimental, and it looks like you've encountered a corner-case. There is a problem in the SSE (`((?a2 "a3") (?a4 "a4"))`...

Typically, when a release is made, the gem versions are set to `~>` and `>=`, although in the case of rdf-raptor, the `~>` was never set. If there's a particular...

On Mar 27, 2015, at 2:18 AM, David Butler [email protected] wrote: > @gkellogg I was interested to know why FFI was pinned to >= 1.9.x, rather than >= 1.0.x as...

That's because in N3, QNames have a prescribed form that disallows the %-encoded URI. A QName has a prefix and a local part, both of which must be NCNames. From...

Loading N-Triples when seeing text/plain is historic, and obsolete. Best to remove support for this directly in the RDF gem.

It's not clear exactly what restriction you're referring to. The link you provided shows the creation of a SPARQL CONSTRUCT using the supplied patterns. Is it that the serialization of...

I don't think there are any official tests for this, and my implementation certainly doesn't raise an error. (Of course, BNodes in predicate locations are never okay). In the case...

Yes, I was thinking much the same (`?node` instead of `_:node`, of course).