-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDF Star Support #43
Comments
Are you sure that GraphDB sends a correct response? If you get something strange from the endpoint itself I doubt this library could be at fault much itself. After all, it's just a fairly simple wrapper which performs the correct request and handles parsing of the response (be it SELECT bindings, triples from CONSTRUCT/DESCRIBE, etc) That said, a parser used by |
@bolerio The result parser doesn't support RDF-star at the moment. I plan to add this feature in the next major version. A catalog of features is in progress, and I will create issues and a milestone this week. The coding part is planned to be done in January. |
@bergos Thanks for the info. Can't promise anything, but I'll monitor and if I find time I could try to contribute with the effort. |
@tpluscode I am not sure that GraphDB sends the correct response, no. Also, I don't know what "correct" is here because I've never seen a spec for "SPARQL Star HTTP Protocol". But that's a good point, there could be a bug there... |
Is RDF/SPARQL Star support? I tried with GraphDB with a query like
The query succeeds and the variables ?p and ?v are instantiated correctly, but instead of the triple I get back some GraphDB internal generated identifier.
SPARQL HTTP Protocol is probably behind on RDF Star....any thoughts?
Apologies if this is not the right forum to ask a question like this - I see the same people in various RDF JavaScript effort, perhaps there is some discussion forum that I should be using.
The text was updated successfully, but these errors were encountered: