This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-02
Channels
- # announcements (7)
- # aws (3)
- # babashka (132)
- # beginners (38)
- # calva (3)
- # chlorine-clover (6)
- # clara (1)
- # clj-kondo (20)
- # cljs-dev (24)
- # cljsrn (9)
- # clojure (76)
- # clojure-dev (1)
- # clojure-germany (4)
- # clojure-india (2)
- # clojure-uk (24)
- # clojurescript (15)
- # conf-proposals (1)
- # conjure (114)
- # cursive (3)
- # fulcro (63)
- # graalvm (1)
- # helix (2)
- # joker (10)
- # juxt (1)
- # local-first-clojure (2)
- # meander (9)
- # off-topic (97)
- # rdf (4)
- # re-frame (7)
- # reagent (16)
- # reitit (1)
- # rum (9)
- # shadow-cljs (48)
- # spacemacs (3)
- # tools-deps (3)
- # vim (30)
- # xtdb (10)
an article that helped me compare between RDF and property graphs (the model of databases like Neo4J and others): http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-herring.html
since you are talking abou t"servers" I'm guessing it could be an interested read to you since it talks about practical/real world data modeling
There’s been movement on reification in RDF since then in that there’s a proposed set of standards RDF*/SPARQL*/Turtle* etc that support edge properties. Whats more at least 4 RDF databases already claim support for it (including stardog), and RDF4j has experimental support available in their native store and memory store implementations too. https://rdf4j.org/documentation/programming/rdfstar/ Reification would definitely be nice in some instances, but you can get by easily enough without it. Also RDF* is not RDF; so I’d be wary of it introducing interop problems, and a more complex data model.
found this thread which answers some questions about addressability and compares RDF* with named graphs https://lists.w3.org/Archives/Public/public-rdf-star/2020Feb/thread.html