You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for a very idiomatic clojure approach to the Jena API. The idea to map Clojure data to ARQ is nice, and frees up from the whole SPARQL query generation. This, indeed seems the a very good data-driven way to achieve that.
I was trying out the API and wondering if you plan to add the property path support, so that we can do recursive and more flexible querying (optional, alternate, but especially the zero/one/more path matches) etc. I think that will open up a bunch of use-cases.
Though, I have worked with both (Clojure/Jena) I am no expert by any means, but I can try to help out.. Tried out with OpPath and TriplePath, but landed into some exceptions.
Thanks and Kudos on releasing this.
The text was updated successfully, but these errors were encountered:
First of all, thanks for a very idiomatic clojure approach to the Jena API. The idea to map Clojure data to ARQ is nice, and frees up from the whole SPARQL query generation. This, indeed seems the a very good data-driven way to achieve that.
I was trying out the API and wondering if you plan to add the property path support, so that we can do recursive and more flexible querying (optional, alternate, but especially the zero/one/more path matches) etc. I think that will open up a bunch of use-cases.
Though, I have worked with both (Clojure/Jena) I am no expert by any means, but I can try to help out.. Tried out with OpPath and TriplePath, but landed into some exceptions.
Thanks and Kudos on releasing this.
The text was updated successfully, but these errors were encountered: