Patrick, The reasons I specified UTF-8 were (1) to be consistent with the rest of the spec (e.g. you don't have to change your thinking just because you are...
1739
John Cowan
johnwcowan
Sep 24, 2011 6:45 pm
... H for Huge might be good. We want people to encode ordinary numbers using the byte/int/double formats. ... Yes. Of course, in this context UTF-8 and...
1738
Patrick Maupin
patmaupin
Sep 24, 2011 6:40 pm
... I like the idea of "encoded generic number". But one of the purposes of a binary encoding is space savings, so I don't think unicode fits into that...
1737
Dennis Gearon
gearond...
Sep 24, 2011 6:34 pm
Since this IS about JAVAscript (not really java, buuuuuuut), use the Java specification for unlimited length integers. Propose it to the javascript/emca ...
1736
rkalla123
Sep 24, 2011 6:23 pm
Hmm! John, I like that idea... it is simple, singular and easy to represent. What would you think of something like this: marker: N length: required example: ...
1735
Dennis Gearon
gearond...
Sep 24, 2011 6:11 pm
I have felt for a LOOOOOONG time, that representing numbers, including drive sizes, integers, any others, could have been future proofed and more simple using...
1734
John Cowan
johnwcowan
Sep 24, 2011 6:01 pm
... Well then, why not add just one more type code for "string-encoded number"? That way, ordinary JSON can be round-tripped with 100% reliability. Well, if...
1733
rkalla123
Sep 24, 2011 5:52 pm
Hey Dennis, Here is where we are: I have been working on a Universal Binary JSON specification and asked the group for feedback on it. You can check the spec...
1732
Dennis Gearon
gearond...
Sep 24, 2011 5:25 pm
this subject in this mail list generated more email in one week that the list had in 6 months. I therefore stepped back, too much to follow. Anyone willing to...
1731
Stephan Beal
stephan.beal
Sep 24, 2011 1:15 pm
... Not beyond the skills - beyond the patience and needs. i host 2 (C and C++) JSON libraries and i have absolutely no need for big numbers, so i would never...
1730
Patrick Maupin
patmaupin
Sep 24, 2011 4:25 am
... The best documentation I know of is in the source for the pickle and pickletools modules. You can find them, e.g. like this: $ python Python 2.6.4...
1729
Tatu Saloranta
cowtowncoder
Sep 24, 2011 3:04 am
... I think it is patronizing to suggest that something as simple as supporting Big Integer and -Decimal would be beyond skills of competent parser writers --...
1728
rkalla123
Sep 23, 2011 4:49 pm
1727
rkalla123
Sep 23, 2011 4:47 pm
Milo, Agreed on how the format must be presented on the website, I am keeping your post bookmarked as a TODO list as I work on formalizing the spec on the...
1726
rkalla123
Sep 23, 2011 4:43 pm
Don, Great feedback so far, I have a few thoughts on the subject: 1. The hard-to-measure value of a specification being simple and immediately grok'able is...
1725
John Cowan
johnwcowan
Sep 23, 2011 4:36 pm
... Unfortunately, the various pickle formats are apparently not documented anywhere that Google can find. Can you provide a pointer? (There is also a...
1724
rkalla123
Sep 23, 2011 4:16 pm
Patrick, Thank you for the pointer....
1723
Patrick Maupin
patmaupin
Sep 23, 2011 3:55 pm
I'm all for big integer support. I use it all the time (from Python). As an aside, as others have pointed out, there are other similar efforts around. If...
1722
Stephan Beal
stephan.beal
Sep 23, 2011 12:47 am
... Absolutely. That's a literal interpretation (but not a sane one, i admit!). ... Interpreted that way, all implementations must implement...
1721
Tatu Saloranta
cowtowncoder
Sep 23, 2011 12:31 am
... I agree with this, and also with the general idea of using most economic applicable type (i.e. not using unlimited-length representation for small...
1720
Tatu Saloranta
cowtowncoder
Sep 23, 2011 12:28 am
... You have a very interesting way of reading specifications -- when spec does not limit magnitude or precision, you claim it's fine to use whatever size: by...
1719
Stephan Beal
stephan.beal
Sep 22, 2011 10:00 pm
On Thu, Sep 22, 2011 at 11:47 PM, Milo Sredkov <miloslav@...> wrote: supported by the specification, and tools try their best to deliver it ... i would...
1718
Milo Sredkov
milosredkov
Sep 22, 2011 9:48 pm
Hello Riyad, Stephan, Don, Tatu, and all group members, I recently analysed about 70 of the libraries linked from json.org (almost all listed in the C++, C,...
1717
Raymond Reggers
adaptivdesign
Sep 22, 2011 9:29 pm
Hey all, It might be worth it, to take a peek at the AMF0 and AMF3 protocol. The AM3 protocol makes a distinction between integer and number data. Taken from...
1716
Don Owens
regexman
Sep 22, 2011 2:33 pm
I forgot to add that encoders should only use the big number format if the number is too big to fit in int64 (or int32, depending on which will be the largest...
1715
Don Owens
regexman
Sep 22, 2011 2:21 pm
I didn't mean to imply that every environment has this support -- I'm very aware that most environments do not. However, the same issue arises when using...
1714
Don Owens
regexman
Sep 22, 2011 2:15 pm
Yes, that is what I was getting at. But see comments embedded. ... complement and such is probably too much work. Maybe just specify that the first bit...
1713
rkalla123
Sep 22, 2011 1:43 pm
Stephan, It reminds me of our conversation earlier about 64-bit. As you mentioned, Don has a great point, but the uniqueness of the data structure (I doubt the...
1712
Stephan Beal
stephan.beal
Sep 22, 2011 7:12 am
... i don't agree: JSON does not specify an integer size, which means that supporting only an 8-bit int is still valid JSON. -- ... ...
1711
Stephan Beal
stephan.beal
Sep 22, 2011 7:11 am
... Correct, format does not aim for minimal complexity of implementations. ... But for the decoder it's required, or at least that's how i understood the ...
