Hi, I believe that, in order to properly/correctly solve this issue, SPARQL implementations could provide a mean to get for each bnode in a SPARQL query answer the data graph node *bound* to it, e.g., for each SPARQL query result there could be a table with bindings: <result-bnode, data-graph-node>. IMHO it would be wrong (and not necessary, in this case) to give persistent identifiers to bnodes. cheers --e. On 10 Dec 2018, at 17:30, David Booth <david@dbooth.org<mailto:david@dbooth.org>> wrote: On 12/10/18 5:34 AM, Michael Brunnbauer wrote: I'd really like to see mandatory persistent blank node identifiers in SPARQL - so I can easily do followup queries for blank nodes from a SPARQL result. Is this a big deal? I think some triples stores can already do this. Which issue do I upvote to get this? Blank nodes #19: https://github.com/w3c/EasierRDF/issues/19 David Booth
Received on Monday, 10 December 2018 17:04:39 UTC