By the way I would not treat Twinkle as a good SPARQL validator. Last I knew Twinkle was using a very outdated version of ARQ which significantly pre-dates the Jena transition into Apache
Use sparql.org as Andy suggests which runs the latest release version, or if you download and run our Fuseki server tool locally it includes the SPARQL validator in its default configuration. Rob On 1/23/13 10:08 AM, "Andy Seaborne" <[email protected]> wrote: >On 22/01/13 23:23, Bardo Nelgen wrote: >> Hi all, >> >> for a content inclusion project I recently wrote the following SPARQL >> query, had it validated at http://sparql.org/query-validator.html and >> tested locally with Twinkle 2 –? all doing perfectly well. >> >> >>> PREFIX html: <http://www.w3.org/1999/xhtml> >>> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> >>> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> >>> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> >>> PREFIX owl: <http://www.w3.org/2002/07/owl#> >>> PREFIX xsd: <urn:ietf:params:xml:schema:> >>> PREFIX dct: <http://purl.org/dc/terms/> >>> PREFIX i18n21: <http://apache.org/cocoon/i18n/2.1> >>> PREFIX xliff: <urn:oasis:names:tc:xliff:document:1.2> >>> PREFIX cnt: <http://namespaces.semaworx.org/content#> >>> PREFIX timed: <http://namespaces.semaworx.org/timed#> >> > >>> CONSTRUCT { ?PageIRI rdf:type cnt:page ; >>> dct:hasPart ?Element . >>> ?Element rdf:type cnt:element >>> ; >>> dct:hasPart >>> ?ElementPayload . >>> ?ElementPayload rdf:type ql >>> timed:versionedElement ; >>> xliff:source >>> ?StringContent . >>> } >>> WHERE { ?PageIRI cnt:pageID >>> "semawine_page_home" ; >>> rdf:type cnt:page ; >>> dct:hasPart ?Element . >>> ?Element rdf:type cnt:element >>> ; >>> dct:hasPart >>> ?ElementPayload . >>> ?ElementPayload rdf:type >>> timed:versionedElement ; >>> xliff:source >>> ?StringContent . >>> FILTER ( isLiteral(?StringContent) >>> || langMatches( >>> lang(?StringContent), "de-de" ) ) >>> } >> >> >> Though, just as soon as this very same query runs on our server, >> JENA/ARQ gives me a >> >>> com.hp.hpl.jena.query.QueryParseException: Syntaxfehler >> >> Which is, why I'm looking for a query validator, which evaluates SPARQL >> more similar to the way JENA/ARQ do? internally and which provides >> errors meaningful enough to properly act upon. >> >> Any help, links, tools etc. are very welcome!! > >http://sparql.org/query-validator.html is running Jena (it is a Fuseki >server). > >Parse errors return the line number and column of the error (being an LL >parser, they are usually right!) > >You have a different error - what's the stacktrace? > > Andy > >> >> Best, >> >> Bardo >> >> >> >> >
