Hi Hasan and all,

I propose the following pragmatic approach to support sparql fastlane
(CLEREZZA-468) and sparql 1.1:

- Drop full query parsing
- Create subclass of TcProvider that accepts sparql query as string
- Have a minimum parsing of the queries to get the names a query is
directed against
- In TcManager route the query to the right TcProvider or fall back to
slow-lane if multiple TcProviders are affected
- This should be part of rdf.core and replace the existing funcionality
tehre

Question:
- Did you already model the results of Sparql 1.1? I think there is no big
difference there to 1.0.

Cheers,
Reto

Reply via email to