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.
Jena's internal model doesn't treat an RDF graph as a set of triples. Instead, repeated triples (meaning triples with the same subject, predicate, and object) are represented as different Java objects, even though they are the same w.r.t. equals. It seems that Jena's internal model repeats triples for blank nodes annotated with
rdf:nodeID="genid3"
, leading to duplicates in our LDTab output.The proposed change fixes this issue. However, it would prevent us from round-tripping files with duplicate triples. This is not exactly desirable. I'll see whether I can come up with a better solution. At least we know where the 'bug' is located.