Hacker News Reader

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?"