Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of LDTab's guiding design choices is to eliminate blank nodes where possible. In the case of existential blank nodes, i.e., blank nodes that do not appear as objects in an RDF graph, we can choose to
i) introduce a 'wiring' blank node for the subject column
ii) use "unknown" for the predicate (or a value of a property that indicates what kind of structure the blank node points to - so far we have chosen its
rdf:type
, if available.)iii) put the JSON structure of the existential blank node in the object column.
OR
Example:
Consider a disjoint classes axiom in OWL. This is represented with an existential blank node in RDF corresponding to the following JSON object in LDTab:
Instead of putting this JSON object in LDTab's object column (as per 1. above), we would unfold the top level of the JSON object into the following two LDTab rows (I'm using CURIEs instead of full IRIs for classes here):