Kendall Clark recently discussed what users can expect from Stardog next. Clark wrote, “The most pressing need in Stardog is support for SPARQL 1.1. We got stuck between the devil and the deep blue sea—trying to push the 1.0 release before the SPARQL Working Group was completely finished with the SPARQL 1.1 spec. We were motivated to avoid reimplementing any parts of SPARQL 1.1 because the spec shifted. So we decided SPARQL 1.10 for the Stardog 1.0 release. Then we told everyone that SPARQL 1.1 would be the highest priority item for the post-1.0 release cycle. And so it’s been.”

He continues, “As of this writing, Stardog TRUNK supports all of SPARQL 1.1 query language; property paths are not totally finished but we’re close. We already support a superset of the HTTP protocol for 1.1, so that’s good.) Finishing property paths, final testing, and tweaking will take a bit longer: we expect Stardog 1.1 release to be out by the end of October. It will include full SPARQL 1.1 support. Except for the bits we don’t like. Frankly we’re nervous about adding update operations to SPARQL (the query language; we already support update in our HTTP and SNARL protocols) because we’re worried about SPARQL injection attacks. So we’re going to take a bit more time to work out a secure design for supporting update operations in the query language. Stay tuned for those bits some time after the 1.1 release.”

Read more here, or consider attending a presentation by Michael H. Grove, Director of Development at Stardog, at this week’s SemTechBiz NYC. Grove’s presentation is entitled Stardog Meets SPARQL 1.1.

Image: Courtesy Stardog