-
Notifications
You must be signed in to change notification settings - Fork 30
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
blank nodes cannot be viewed as subjects #77
Comments
At least with GraphDB, I might have found a workaround but it's specific for GraphDB. It's possible to get the internal GraphDB ID of each URI, BN, literal, etc.: http://graphdb.ontotext.com/documentation/free/query-behaviour.html?highlight=blank%20node With the following query, the ID can be retrieved of a BN:
And with this query, the ID (xsd:long, eg 5660) can be used to query information
|
A more generic solution might be to find blank nodes by matching their projected string.
This works for Stardog, but sadly not for GraphDB... (empty strings are returned for |
Expected Behavior
Being able to view triples with a BN as the subject, either through the details view on the BN when in object position or when focusing on the BN directly.
Actual Behavior
I can see BNs appear in the facet browser list and when viewing individual resources as long as the BNs are in the object position of triples. If I want to view details of a BN object, I cannot see the triples with this BN as the subject. If I click on the blank node, I end up on an empty LD-R page of that BN (no triples are shown, only the BN ID is presented). I played a bit with the settings in
reactor.js
for the property pointing to BNs and sethasBlankNode: 1
, but without success.I did some tests with GraphDB and Stardog.
With GraphDB, I receive an error from GraphDB, that it received an erroneous SPARQL query (BN is treated as an absolute URI):
'MALFORMED QUERY: Not a valid (absolute) IRI: genid-0ec5327183c642a3aff8f0b3208583c7-130'
With Stardog, I only get an error from LD-R
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: