Yes I thought you guys did support them Of course the actual user has yet to tell us any version information (either Jena, Virtuoso or the Virtuoso Jena Provider) nor have they provided us an error message so we¹re all really just speculating here.
Anila - Please can you confirm your versions for all components and provide the error message you get otherwise we cannot help you further Regards, Rob On 10/04/2014 16:41, "Hugh Williams" <[email protected]> wrote: >Hi Andy > >The Virtuoso Jena Provider was updated last year to support Jena 2.10 and >has also been tested with the latest Jena 2.11 release available for >download. > >Virtuoso does support SPARQL 1.1 Property Paths as indicated at: > > > http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtTipsAndTri >cksSPARQL11PropertyPaths > >The query is using the property path "+" unary operator which is standard >SPARQL 1.1 I believe ? > >Best Regards >Hugh Williams >Professional Services >OpenLink Software, Inc. // http://www.openlinksw.com/ >Weblog -- http://www.openlinksw.com/blogs/ >LinkedIn -- http://www.linkedin.com/company/openlink-software/ >Twitter -- http://twitter.com/OpenLink >Google+ -- http://plus.google.com/100570109519069333827/ >Facebook -- http://www.facebook.com/OpenLinkSoftware >Universal Data Access, Integration, and Management Technology Providers > >On 10 Apr 2014, at 18:29, Andy Seaborne <[email protected]> wrote: > >> On 10/04/14 16:12, Rob Vesse wrote: >>> The Jena SPARQL parser is actually generated from the same grammar that >>> was used to generate the grammar in the official specification so yes >>>we >>> fully support SPARQL 1.1 and have done for all releases in the past >>> year/so. >>> >>> Rob >> >> Right! >> >> The version of Jena used by Virtuoso in their adapter has been reported >>to be quite old. >> >> However, in this case the problem looks like it is because Virtuoso is >>not SPARQL 1.1 compliant. It does not support property paths. They >>have their own syntax. >> >> Andy >> >>> >>> On 10/04/2014 03:43, "Hugh Williams" <[email protected]> wrote: >>> >>>> Hi >>>> >>>> See the following Virtuoso Jena Provider documentation link on how to >>>>by >>>> the Jena/ARQ parser: >>>> >>>> >>>> http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtJenaPro >>>>vid >>>> er#Bypass%20Jena/ARQ%20parser >>>> >>>> As if the query runs against the Virtuoso SPARQL endpoint or directly >>>> from "isql" then you should be able to get it to run via Jena by >>>> "bypassing" its parser, assuming that is what is generating the yet >>>>to be >>>> seen error. >>>> >>>> Having said that I would have thought the latest Jena versions are >>>>SPARQL >>>> 1.1 compliant ? >>>> >>>> Best Regards >>>> Hugh Williams >>>> Professional Services >>>> OpenLink Software, Inc. // >>>>http://www.openlinksw.com/ >>>> Weblog -- http://www.openlinksw.com/blogs/ >>>> LinkedIn -- http://www.linkedin.com/company/openlink-software/ >>>> Twitter -- http://twitter.com/OpenLink >>>> Google+ -- http://plus.google.com/100570109519069333827/ >>>> Facebook -- http://www.facebook.com/OpenLinkSoftware >>>> Universal Data Access, Integration, and Management Technology >>>>Providers >>>> >>>> On 10 Apr 2014, at 10:18, Olivier Rossel <[email protected]> >>>>wrote: >>>> >>>>> I have had some problems with a very old ARQ library version I am >>>>>stuck >>>>> with. >>>>> The parser was not understanding some SPARQL1.1 statements. >>>>> >>>>> Andy proposed to upgrade ARQ to the latest version. >>>>> Or to send the query directy via HTTP without using the Jena helpful >>>>> functions. >>>>> I took the second option. >>>>> My code went from this: >>>>> Query query = QueryFactory.create(queryString); >>>>> QueryExecution qexec = QueryExecutionFactory.sparqlService(service, >>>>> query); >>>>> ResultSet resultSet = qexec.execSelect(); >>>>> >>>>> to this: >>>>> QueryExecution qexec = new QueryEngineHTTP(service, queryString); >>>>> ResultSet resultSet = qexec.execSelect(); >>>>> >>>>> >>>>> Hope it helps... >>>>> >>>>> >>>>> >>>>> On Thu, Apr 10, 2014 at 10:31 AM, Damian Steer <[email protected]> >>>>> wrote: >>>>> >>>>>> On 10/04/14 06:15, Anila Sahar Butt wrote: >>>>>>> PREFIX csiro:<http://au.csiro.browser#> >>>>>>> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#> >>>>>>> PREFIX owl:<http://www.w3.org/2002/07/owl#> >>>>>>> PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> >>>>>>> >>>>>>> SELECT ?property ?propLabel ?range ?rangeLabel >>>>>>> WHERE {{{<http://xmlns.com/foaf/0.1/Agent> rdfs:subClassOf+ ?res. >>>>>>>?res >>>>>>> owl:onProperty ?property.} UNION >>>>>>>{{<http://xmlns.com/foaf/0.1/Agent> >>>>>>> rdfs:subClassOf+ ?class. ?property rdfs:domain ?class.} UNION >>>>>>> {?property >>>>>>> rdfs:domain <http://xmlns.com/foaf/0.1/Agent>}} } {{?res ?resProp >>>>>>> ?range.FILTER ((?resProp = owl:allValuesFrom) || (?resProp = >>>>>>> owl:someValuesFrom) )} UNION {?property rdfs:range ?range.}} >>>>>>>OPTIONAL >>>>>>> {?property rdfs:label ?propLabel.} Optional {?range rdfs:label >>>>>>> ?rangeLabel.}} >>>>>> >>>>>> I just tried this using the sparql.org validator (which uses jena) >>>>>>and >>>>>> it's fine. >>>>>> >>>>>> What error are you getting? >>>>>> >>>>>> Damian >>>>>> >>>> >>> >>> >>> >>> >> >
