Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JSONx is an IBM standard format to represent JSON as XML

publib.boulder.ibm.com

Post reply on HN
Print view View original

21–30 of 80 posts

Re: JSONx is an IBM standard format to represent JSON as XML

#21

Post by haberman »

js2 wrote: post #12

Reminds me of the Property List evolution: 1. "Under NeXTSTEP, property lists were designed to be human-readable and edited by hand, serialized to ASCII in a syntax somewhat like a programming language." 2. "In Mac OS X 10.0, the NeXTSTEP format was deprecated, and a new XML format was introduced." 3. "Since XML files, however, are not the most space-efficient means of storage, Mac OS X 10.2 introduced a new format w…

Everything converges to the equivalent of protocol buffers.

Property lists -> XML -> Binary Property Lists

JSON -> JSON Schema -> Binary JSON

XML -> XML Schema -> XML Namespaces -> Binary XML

Or you can skip all that faffing around and just jump straight to protocol buffers. :)

ps. Protocol Buffers have a text format too that looks very similar to JSON. And you can encode protocol buffers as JSON, though I'm not sure there's good software support for it yet. I'm working on it.

Re: JSONx is an IBM standard format to represent JSON as XML

#22

Post by rpeden »

This comes from the docs for the DataPower XML Security Appliance. Naturally, I was curious about what this Appliance does.

If you go up the tree a bit, click Development, then XML Firewall, then Introduction, you'll find this tidbit:

"These appliances offer an innovative, pragmatic approach to harness the power of SOA while simultaneously enabling you to leverage the value of your existing application, security, and networking infrastructure investments."

Seems like a great attempt to use as many words as possible to say nothing at all. :)

Re: JSONx is an IBM standard format to represent JSON as XML

#23

Post by ericmoritz »

gte910h wrote: post #6
drawkbox wrote: post #3

Why oh why... If it helps JSON invade the enterprise then ok, but why make a good thing bad.

http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde... To allow you to use XSLT tools apparently.

XSLT and XPath is about the only reason I can see to use this. But, you know, how hard is:

   x.person.addresses[0].city?
I guess XPath is easier when you probably have to do something like this:

   JSONObject json = (JSONObject) JSONSerializer.toJSON( jsonTxt )
   String city = json.getJSONObject("person").getJSONArray("addresses").getJSONObject(0).getJSONObject("city");
Or however you'd do it in Java.

Re: JSONx is an IBM standard format to represent JSON as XML

#25

Post by wulczer »

Not sure what all the fuss is about. It's actually neat to have a common way of changing JSON to XML, think of a web service that offers an API using our beloved JSON. But wait, we also want to provide an XML API! Let's design our own, ad-hoc, crappy mapping or... use that thing that everyone else is using.

XML is out there, has lots of tools and libraries and is actually useful for some things. Not to mention the array of technologies around it, like XPath, XQuery etc, that JSON is lacking (probably because it doesn't need it, because these formats do address slightly different requirements. Gasp!).

Re: JSONx is an IBM standard format to represent JSON as XML

#26

Post by buddydvd »

rpeden wrote: post #22

This comes from the docs for the DataPower XML Security Appliance. Naturally, I was curious about what this Appliance does. If you go up the tree a bit, click Development, then XML Firewall, then Introduction, you'll find this tidbit: "These appliances offer an innovative, pragmatic approach to harness the power of SOA while simultaneously enabling you to leverage the value of your existing application, security, and…

This point seems relevant:

"Bridges to Web 2.0 technologies with JSON filtering and validation, support for REST verbs, and converting/bridging of REST and Web services."

http://www-01.ibm.com/software/integration/datapower/xs40/

Re: JSONx is an IBM standard format to represent JSON as XML

#27

Post by wulczer »

seiji wrote: post #14
buddydvd wrote: post #9

"In an XML Firewall service, JSONx can be used like other XML input." http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde... "An XML firewall is a specialized device used to protect applications exposed through XML based interfaces like WSDL and REST and scan XML traffic coming in and out of an organization. [snipped] XML Firewall is often used to validate XML traffic, control access to XML based resources,…

Also, http://en.wikipedia.org/wiki/XML_appliance and http://www.layer7tech.com/products/xml-accelerator Astounding, is it not?

all common XML message formats including POX (Plain Old XML), SOAP, REST and AJAX

That made my day.

Re: JSONx is an IBM standard format to represent JSON as XML

#28

Post by Sitwon »

albertogh wrote: post #10

Using the example from http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde... muk:~ fiam$ echo '{ "name":"John Smith"... }'|wc -c 303 muk:~ fiam$ echo ' … ' |wc -c 904 I don't really have anything else to say. Edit: formatting

The example may be unnecessarily verbose (for example, they would have saved 90 characters by using json as the default namespace), but this is text. It's ridiculously compressible. Saving a handful of characters here or there is probably wasted effort.

Re: JSONx is an IBM standard format to represent JSON as XML

#30

Post by jerf »

seiji wrote: post #14
buddydvd wrote: post #9

"In an XML Firewall service, JSONx can be used like other XML input." http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde... "An XML firewall is a specialized device used to protect applications exposed through XML based interfaces like WSDL and REST and scan XML traffic coming in and out of an organization. [snipped] XML Firewall is often used to validate XML traffic, control access to XML based resources,…

Also, http://en.wikipedia.org/wiki/XML_appliance and http://www.layer7tech.com/products/xml-accelerator Astounding, is it not?

It's less silly than it sounds. Many XML attacks have JSON equivalents. Do you know how your JSON parser will deal with 512KB of open square brackets in a row?
Post reply on HN