support SPARQL 1.1 property paths

[christopher-johnson]

This would be very useful for what I am trying to do with your awesome product.

Here is the spec. A predicate can be either a URI or a path construct.

I started to implement this here. The Matcher only checks for an asterisk for now.

However, I realized that this is more involved than I had anticipated. A decision tree has to made to route property path type queries to SELECT and normal ones to CONSTRUCT. And if it is a SELECT then an Accept header has to be sent to make sure that the response is N3/turtle.

Thanks!

[RubenVerborgh]

Thanks, @christopher-johnson. Property paths are one of the more expensive features of SPARQL 1.1. Creating support is possible, but will likely always be slow with a TPF interface.