Hi Minto With you update to the latest jena we got closer to it :)
The plan is to drop the query parsing in clerezza and forward the query as a string to the QueryableTcProvider (i.e. a provider supporting fastlane) or to use the backend independent implementation (based on jena arq). As the result formats didn't change with this changes sparql 1.1 will be supported. What there is todo is: - Adapt QueryEngine to take a String rather than a query - Adapt implementation (arq based) and client of the QueryEngine - Make TdbTcProvider implement QueryableTcProvider - Forward query to fast- or slowlane using the Preparerser Hasan recently implemented Cheers, Reto On Fri, Apr 26, 2013 at 9:52 AM, Minto van der Sluis <[email protected]>wrote: > Hi, > > I was wondering what the current status is on supporting sparql 1.1? > > Can I be of any help? > > Please let me know. > > Regards, > > Minto >
