Re:Publishing JSON-LD for Developers
by athenot on Tuesday May 08, 2018 @01:55PM
(#17023014)
I guess I don't understand the purpose. If a high degree of formalization, typing and namespacing is required, why not use full-blown XML with namespaces and schemas?
[ Parent
| on HN ]
Everyone is slowly reinventing SOAP :)
(Note that RDF can modelize graphs natively, has native support of types, IDs and labels, and has a javascript parsing library, a bit more powerful than JSON.parse()).
Because XML is a much worse match for everyone's data model than JSON is.
Data structures aren't marked-up text. And that one time that XML was supposed to be used for marked-up text (XHTML), it wasn't even good at that either.
Re:Publishing JSON-LD for Developers
by goofballlogic on Tuesday May 08, 2018 @04:05PM
(#17024412)
A json-based format still has some advantages depending on context. E.g. JavaScript code can manipulate JSON data "natively" whereas XML support is far harder to achieve.