SPARQL for RDF querying <https://twitter.com/bobdc...
# thinking-togetherc
Chris G
04/26/2020, 7:29 PMSPARQL for RDF querying https://twitter.com/bobdc/status/1254431101440983043
đ€© 2
e
Emmanuel Oga
04/26/2020, 9:57 PM"I use these rarely enough that I re-read the âNamed Graphsâ section of my bookâs âUpdating Data with SPARQLâ chapter as a review before I assembled the steps below."
Emmanuel Oga
04/26/2020, 9:58 PMthis is weird to me since it seems like such useful feature, given the difficulty to address triples. The named graph makes the triple a quad
Emmanuel Oga
04/26/2020, 9:58 PMso you can use that forth quad to determine origin of the triple for instance
Emmanuel Oga
04/26/2020, 9:59 PMif the graph is named "emmanuel:2020-04-26" then potentially I can use that info to determine author and date of each of the triples on that graph
đ 1
j
Jared Windover
04/27/2020, 2:05 PMThe author makes two (on the surface) contradictory claims: redundancy generally leads to inefficiency, and db administrators introduce redundancy to increase efficiency. I think in the first case, theyâre referring to developer/user efficiency, and in the second computer (db server) efficiency. Other ways that we can trade off between those two efficiencies spring to mind: low-level vs. high-level languages, simple vs. complex UI. Pretty unrelated to the content of the article, but I thought it was a little interesting.
e
Emmanuel Oga
04/27/2020, 6:56 PMI found the comment on inefficiency weird too... denormalization is wasteful in terms of storage requirements but it is usually done to avoid joins, so it ends up being a trade-off, the main problem it causes is not inefficiency but data inconsistency
Emmanuel Oga
05/12/2020, 2:41 AMoh, been reading these patterns on using named graphs: https://patterns.dataincubator.org/book/data-management-patterns.html
3 Views