Skip to content
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

SPARQL fails if we encounter a node which is never a subject #1

Closed
patrickmcelwee opened this issue Jul 25, 2017 · 1 comment
Closed

Comments

@patrickmcelwee
Copy link
Owner

If one of the connected nodes is only an object (and literally has no triples in which it is a subject), our back-end library errors out because it gets no results for a crucial SPARQL query. I think these lines are unnecessary: https://github.com/patrickmcelwee/mlpm-visjs-graph/blob/master/visjs-lib.xqy#L59-L61 ... we don't have any reason to check to be sure that it is a subject somewhere.

@patrickmcelwee
Copy link
Owner Author

This also seems to be connected to the case where there are multiple types for a subject, which causes an exception like this: patrickmcelwee/ml-visjs-graph-ng#19 ... for now, it is probably best to add LIMIT 1 to this line: https://github.com/patrickmcelwee/mlpm-visjs-graph/blob/master/visjs-lib.xqy#L68 ... this will just take a type at random, which perhaps isn't the best, but it is better than breaking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant