Exception SPARQL Query caused through wildcard

[galigator]

Exception SPARQL Query caused through wildcard

[LorenzBuehmann]

I don't think that SPARQL-DL supports SPARQL 1.1 property paths.

[greeny277]

Ok. I was just wondering why the SPARQL plugin by Protege can handle this query. Meanwhile i thought about replacing this intersectionOf with a bunch of subclassOf relations. So I guess this is no bug then?

[Galigator]

Anything that end with that kind of Exception should be see as a bug.
The tool should send at least a better error message.

I'm not very awar of how the sparql-query module work and maybe I have done a bad mistake somewhere.

What version are you using ?

[greeny277]

I'm currently using version 2.6.2.

[LorenzBuehmann]

@greeny277 Which SPARQL plugin do you use? Protege has two SPARQL plugins:

1. The standard SPARQL query tab doesn't use Pellet and doesn't support DL reasoning. It uses RDF4J as SPARQL API and support property paths.
2. The Snap SPARQL plugin uses its own parser + SPARQL DL API, but this plugin does not support Property Paths.

<dependency>
            <groupId>edu.stanford.protege</groupId>
            <artifactId>de-derivo-sparqldlapi</artifactId>
            <version>3.0.0</version>
        </dependency>

Pellet is using SPARQL DL which doesn't support property paths.

[greeny277]

I'm using the Standard SPARQL Query Plugin in Version 2.0.2.

[LorenzBuehmann]

Ok, as I said, this plugin uses RDF4J for SPARQL query processing.
Regarding Pellet, its SPARQL query API was developed before SPARQL 1.1, so that might be the reason for missing support. At least I assume that the parser fails somehow. Maybe it's easy to fix, but somebody would have to dig into the code.

Your current query doesn't look like reasoning is necessary. You can use standard Apache Jena if you don't need OWL DL reasoning. Jena also supports some rule-based reasoning for different language profiles, maybe that would be sufficient just in case you need some light-weight reasoning.