RDFLib/rdflib — Issue #110: decide what to do with sparql support
Author: gjhiggins
Created: 2012-02-20 08:32:59+00:00
State: open

eik...@gmail.com, 2010-02-09T15:24:06.000Z

The sparql support currently has a bunch of issues and is in need of some major cleanup. We've
recently removed a fair amount of unmaintained/unstable code from rdflib (all non core
functionality and mostly store implementations). If we hope to release rdflib 2.5.0 anytime soon
we will likely need to remove the sparql support (despite it being arguable more core than an
arbitrary store implementation).

If and when we get the sparql support into a more solid and working state we can include it back
into rdflib proper. Perhaps if we get enough of the original authors helping out we can work
though the issues in time for a 2.5 release like we did for the rest of the issues. Else let's work
on the sparql support over in the rdfextra project.

The sparql support already plugs into rdflib as a plugin and so separating it into its own release
should be straightforward.

Comment 1 by eik...@gmail.com
This issue was updated by revision r1844.

Moving to rdfextra for the time being

Comment 2 by rufus.po...@gmail.com
Hope you realize this has immediately broken HEAD -- setup.py still references (now
non-existent) rdflib/sparql package ...

Comment 3 by gromgull
i removed the package from setup.py in r1846

Comment 4 by eik...@gmail.com
These issues involve bits that have been moved out of rdflib proper for now. We will re-open them
or move them to rdfextas as appropriate.

Comment 5 by chime...@gmail.com
See: http://code.google.com/p/rdflib/source/detail?r=1861

Comment 6 by eik...@gmail.com
Thank you Chimezie for committing the your latest sparql code. There's a number of us that are willing to
help stabilize the code and fix up the issues, but we were having a hard time getting our arms around the
code. Ideally we can make a plan and all help get the sparql support added back to trunk.

I noticed the branch is called sparql2sql; does the implementation depend on the store being an sql one? I
noticed a fair amount of sparql code in trunk depended on the mysql store related code when I was moving it
out of trunk.

I'll update the Roadmap now and add a section for a sparql plan.

Comment 7 by eik...@gmail.com
This issue was updated by revision 29c368cce983.

Moving to rdfextra for the time being

Comment 8 by gromgull
(cleaning up issue list)