Hi Reto On Sat, Feb 23, 2013 at 10:04 PM, Reto Bachmann-Gmür <r...@apache.org>wrote:
> Hi Hasan and all, > > I propose the following pragmatic approach to support sparql fastlane > (CLEREZZA-468) and sparql 1.1: > > - Drop full query parsing > ok. > - Create subclass of TcProvider that accepts sparql query as string > Assumed that this string will be used when invoking the underlying engine > - Have a minimum parsing of the queries to get the names a query is > directed against > this would be the datasetclause of the "sparql query" and in case of "sparql update" it would be the graphref. So we need a simple parser to extract iri of the affected graphs. How should the interface definition of the parser look like for sparql update? > - 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 > ok > > Question: > - Did you already model the results of Sparql 1.1? I think there is no big > difference there to 1.0. > afaik it is the same for query, but a sparql update results in success or failure. cheers hasan > > Cheers, > Reto >
