Hacker News Reader

Comment by berkes | Hacker News Reader

Every time I get to work with JSON-LD (and json-schema and so on) I keep asking myself: how is this better than XML? (I am convinced it isn't).

View on HN

I was just thinking this looks similar to a DDI (Data Documentation Initiative) citation element, but the advantage of the DDI XML schema is that one can annotate any existing element in an XML document by importing the DDI namespace, which shouldn't change how the document is otherwise interpreted by applications, but this JSON schema as far as I can tell is a stand-alone document?

JSON-LD is definitely designed, at least partially, to do the "annotate a preexisting document" thing. You can add the "context" and have it specify the RDF semantics that should apply to each preexisting key.

json-schema has nothing to do with JSON-LD. If you want shape constraints on your JSON-LD data, you'll need SHACL: https://www.w3.org/TR/shacl/

JSON itself has a much simpler specification than XML, and feels much more lightweight for a lot of devs.

Under the hood though, linked data is all RDF.

"Over the hood" JSON is less complicated but less correct than XML, not a good positioning for long-term data storage.

Are you claiming that A: plain (non-LD) JSON is less correct than plain XML, or that B: JSON-LD is less correct than RDF/XML?

I wasn't implying they are related in that way.

Just that both make me think "this thing has long been solved in XML, why re-invent it in JSON?"

Reply on news.ycombinator.com