Open jeswr opened 2 years ago
A big 👍 from me on this. Would be crucial for things like https://github.com/comunica/comunica/issues/873.
An alternative approach could be to store this id
value within the RDF/JS Term
, but not sure which approach would be more convenient.
allternative approach could be to store this id value within the RDF/JS Term
My main concern with this approach would be having to handle conflicting ID's if there are multiple sources.
My main concern with this approach would be having to handle conflicting ID's if there are multiple sources.
Indeed, we'll need a way of detecting distinct sources if we'd go this route (not saying we should). (I did something similar to that here: https://rdfostrich.github.io/article-jws2018-ostrich/#dictionary)
Would look something like
The point of this is to enable multiple sources to share the same
EntityIndex
for memory/performance reasons.Pinging @jacoscaz who may have already done something similar with scoping in quadstore.