| Re: [rdf4j-dev] Relocate InverseMagicProperty |
It won't be an API breakage if we retain the same package names as before and just move module. And queryalgebra-evaluation is already a dependency of spin/lucene so people's existing builds should still work too. It would definitely mean we can share more stuff between spin and the new lucene stuff.On 6 Oct. 2016, at 03:31, Jacek Grzebyta <grzebyta.dev@xxxxxxxxx> wrote:Dear All,I suggest to relocate InverseMagicProperty from rdf4j-spin to rdf4j-queryalgebra-evaluation package to keep it together with TupleFunction.In the above task Mark Hale created an instance of magic property (spin function) which should implement InverseMagicProperty interface. Because of that I added rdf4j-spin dependency into rdf4j-sail-lucene-api. After I found a cyclic reference error:I guess that makes sense. It’s an API breakage, but then again the SPIN stuff is still branded beta, so I can live with shifting things a bit. Perhaps leave a deprecated empty subclass in the old location.More generally I’m thinking that a lot of the TupleFunction implementations have applicability beyond SPIN reasoning. Should we perhaps move all them into the queryalgebra-evaluation package so that we can also (optionally) support their use in “normal” SPARQL queries (when using an extended evaluation strategy)? Or are there obstacles to that that I haven’t seen?Jeen_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rdf4j-dev