The RDF structure is a graph of typed instances of typed objects, serializable as text.

Exchanging RDF, more precisely its [more readable] "RDF/turtle" variant, is probably what will eventually come to the market somehow.

Each object of a RDF structure has a global unique identifier, is typed, maintains typed links with other objects, have typed values.

For an example of RDF being exchanged between a server and a client, you can test

https://search.datao.net/beta/?q=barack%20obama

Open your javascript console, and hover the results on the left hand side of the page with your mouse. The console will display which RDF message triggered the viz in the center of the page.

Update: you may want to FIRST select the facet "DBPedia" at the top of the page, for more meaningful messages exchanged.

Update2: the console does not do syntax higlighting, so here is the highlighted RDF https://datao.net/ttl.jpg linked to the 1st item of " https://search.datao.net/beta/?q=films%20about%20barack%20ob... "

That's a circular argument. What serialization format would you recommend? JSON?

Turtle directly.

JSON forces you to fit your graph of data into a tree structure, that is poorly capturing the cardinalities of the original graph.

Plus of course, the concept of object type is not existing in JSON.

Thank you, I did not realize that RDF has its own serialization format. I'm reading about it now.