Re:JSONx is an IBM standard format to represent JSON as XML
by kamaal on Saturday April 30, 2011 @03:17AM
(#2500090)
This whole thing about not speaking about something wrong ultimately leads to right stuff being lost. Enterprise vendors like IBM are always in the hunt of giving the industry something that forces volumes of people to use it, and then design tools around it that make people addicted to it.
Just put a auto completion feature in a couple famous IDE's to enable this happen, and see how many people use it without caring what, why and how of it.
Then one fine day there is situation that most of the programmers in the market are trained to use it and if you have to run a project you to hire them and let them to what they want. And then the technology adoption grows.
Its not OK just to remain silent. Proper criticism is needed often, it helps things evolve in the right direction.
jsonx is not (neither it is meant to be): - a replacement for json - a format that enables you to query json in a xml database - a standard (I would remember if I was part of a standard comity, although I do recall playing bullshit bingo in some of these meetings)
I think the use case for jsonx is extremely small: maybe exclusively related to transmitting json over the wire in hardware that is specialized for xml processing. Having worked in it I argued many times that it is not even a queryable format, which makes it less usable even in "xml world". ( for a queryable format example you can check isubiker/mljson@github )
If you are not trying to achieve 1) you can/should simply disregard jsonx. That's certainly what I do: It's completely irrelevant for me and even thought I worked on it I never used it in any of my projects. Why should I? You can't query that crap for the heck of it.
About saying crap about IBM: That's just plain stupid. The fact that you can't understand something simply means you can't understand it and not that it is of no value. "all I know is that I know nothing." - Socrates, supposed to be smart guy