Cart
[Home] [By Thread] [By Date] [Recent Entries]
Alan Gutierrez wrote: >> For some time now we've seen the JSON "fat-free alternative to XML" > >> I'm not sure what to make of all this, other than that there is a >> lot of dissatisfaction with the status quo with respect to XML and >> programming, and a lot of experimentation going on to address it. >> Some approaches might threaten XML's story as a universal data >> interchange format, or might revitalize it by scraping off the >> cruft, we shall see. A few questions I'd be interested in hearing >> others' take on: > >> - I'm trying to understand whether JSON has a value proposition >> outside of AJAX scenarios. Is JSON or Python significantly faster >> to parse into usable objects than data-bound XML? Is anyone >> suggesting it (or some Pythonic equivalent) to address the types >> of use cases that binary XML is targeted at? > > Doe JSON address binary? > > It serializes to JavaScript data structures populated with > literals, so it can only handle text data. > > Binary data would have to be encoded to text, just like XML. There's another, perhaps more important issue. JSON assumes that string literals are Unicode; however, it doesn't appear to specify anything regarding how Unicode characters are supposed to be translated into bytes. The examples are trite, providing only representations of ASCII data. You can therefore be absolutely sure that there will be character encoding conflicts as implementers decide on their own what the character encoding ought to be. The declaration and content model for comments is also implicit. -- Chris Burdess
|
