nitter
Stefan Tilkov
@stilkov
22 Oct 2013
Agreement seems to be AtomPub hasn't caught on because of XML. So why is there no standardized JSON variant?
Oct 22, 2013 · 12:21 PM UTC
7
2
4
Mike Amundsen @mamund@mastodon.social
@mamund
22 Oct 2013
Replying to
@stilkov
@stilkov
I respectfully submit that Collection+JSON was designed to fill that slot ;)
1
2
2
Stefan Tilkov
@stilkov
22 Oct 2013
@mamund
Understood and appreciated. Still doesn't explain why no-one did it with AtomPub proper and standardized it, does it?
2
more replies
Stefan Tilkov
@stilkov
22 Oct 2013
@prushforth
I don't know. Nearly all APIs I see (>90%?) use JSON
David Zuelke
@dzuelke
22 Oct 2013
Replying to
@stilkov
@stilkov
I wish people understood that XML's and JSON's use cases hardly intersect. Good luck marking up documents (mixed content!) in JSON…
2
1
1
Stefan Tilkov
@stilkov
22 Oct 2013
@dzuelke
Or putting arrays and records in XML :-)
threads.net/@is_assaf
@assaf
22 Oct 2013
Replying to
@stilkov
@stilkov
because it didn’t deliver any benefit in the XML world, and JSON is about keeping complexity low?
1
Stefan Tilkov
@stilkov
22 Oct 2013
@assaf
I don't agree thousands of specific APIs are less complex
4
more replies
Thomas Steiner
@tomayac
22 Oct 2013
Replying to
@stilkov
@stilkov
I blame the "
#AtomPub
? Nein danke" movement ;-)
upload.wikimedia.org/wikiped…
. On a more serious note, why b/o
#XML
? [citation needed]
Peter Keane
@pkeane
22 Oct 2013
Replying to
@stilkov
@stilkov
JSON is so simple folks didn't see benefit of standardization. Which is really sad since Atompub enables true REST.
threads.net/@is_assaf
@assaf
22 Oct 2013
Replying to
@stilkov
@stilkov
I think there was a belief REST + common formats will make API developing easy; the answer turned out to be SDKs.
Load more