@ammaratef45 @passngrin RDF is an abstract representation of information where things are triples of Subject Predicate Object relations (and realistically quads, adding the contextual "Graph" as one more).

It's pretty cool if you're interested in eg Prolog-style thinking, graphs are great ways to represent known knowledge in many ways.

RDF combines this with a whole ecosystem of things that turns the web into a database of sorts. (A very lossy, untrustworthy database, but a damn cool set of ideas there.)

But they're not a great way of representing *structured* data, which is what most people want in protocols. They are rootless soup.

@ammaratef45 @passngrin Turtle is a particular *encoding* of RDF, a way of writing it down in text. RDF itself is the abstract datatypes, the "platonic ideal" of triples/quads of information, and so you need to encode it to save it in a file or show it to some one. RDF fans often love Turtle because it's a way of writing things down that looks good once you've bought into that mindset.

However, when you get over to eg json-ld, the question is whether or not json-ld is "just an encoding of RDF", and there be dragons, because json-ld also contains other relevant semantic structure, which is to say: structure. And that structure is lost upon conversion to RDF soup.

Also RDF doesn't have ordered lists so just wait till you find out what kind of linked list nightmares happen when you turn an ordered JSON list into RDF.

If you don't know how to interpret the phrase "cons'ing together blank nodes" thank your lucky stars