Hacker News Reader

Comment by ape4 | Hacker News Reader

I agree that XML is only slightly more verbose than JSON but they should still make a JSON version of the spec or it will die. It should be pretty straight forward to mechanically change the XML into JSON.

View on HN

They did: "XEP-0295: JSON Encodings for XMPP" https://xmpp.org/extensions/xep-0295.html

:-)

How about that! Then they need to publicize it. Make a website, say, jmpp.org (pronounced "jump") and a reference implementation.

You might want to read it. :-) The problem has mostly been that nobody's come up with a better JSON representation than one in a April 1st XEP (and they have been proposed - as ralphm says, they're mostly XML-with-curly-brackets, which makes them have the disadvantages of both).

On the other hand, both stanza.io and XMPP-FTW both use the same fixed-format (ie, inextensible) JSON format for XMPP just fine. They can do this because they drop unknown namespaces and don't intend to provide round-trip conversions, etc. So if you're after a JSON "interface" to XMPP, there is one, and it's pretty good.

Worth a look.

Oh yeah (about it being a joke). Thanks for the other pointers.

> NOTICE: This document is Humorous. It MAY provide amusement but SHOULD NOT be taken seriously.

EDIT: Also the X in XMPP stands for eXtensible not XML

Serialization and de-serialisation should be abstracted. I should be able to use JSON, XML, TOML, YAML or MessagePack and just write a plugin.

Reply on news.ycombinator.com