Loading ...
Sorry, an error occurred while loading the content.
Advanced Search
Author
Subject
Message
Special notice only

264 results from messages in json

Advanced Search
  • Thanks.
    douglas@... Mar 23
  • ...I moved to GitHub New repo: https://github.com/tugrul/aspjson Old repo: https://code.google.com/p/aspjson/ On 13.03.2015 18:01, douglas@^$2 [json] wrote: Google has announced that it is shutting down Google Code. If you have a library that is hosted there, please...
    Douglas Crockford Mar 21
  • Google has announced that it is shutting down Google Code. If you have a library that is hosted there, please move it somewhere else. If you tell us here the new location, I will update the list on JSON.org. Bidding farewell to Google Code Bidding farewell to Google Code When we started the Google Code project hosting service in 2006, the world of project hosting was limited. View...
    douglas@... Mar 13
  • Fetching Sponsored Content...
  • {} means an empty object. JSON doesn't say what null means.
    douglas@... Dec 8, 2014
  • JSON is now a formal international data processing standard. http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
    douglas@... Oct 9, 2013
  • IETF and ECMA are working together to draft a JSON standard. You are welcome to participate. The following is is a message that to the members of ECMA TC39: Greetings. As you are probably aware, the IETF is doing a revision to RFC 4627, the document that defines JSON for the Internet. That work is just beginning, and if any members of TC39 would like to participate in it, getting...
    douglascrockford Jun 5, 2013
  • --- In json@^$1, Dave Gamble wrote: > > --- In json@^$2 > 'json%40yahoogroups.com');>, Dave Gamble wrote: > > > Will be very appreciative of any thought/feedback on the matter. Sorry if > > > this one has come up before and I've not seen the thread. > > > > Have you read the JSON RFC? http://www.ietf.org/rfc/rfc4627.txt > > > > Of course. However, in the wild, there appears (and...
    douglascrockford May 26, 2013
  • --- In json@^$1, Dave Gamble wrote: > Will be very appreciative of any thought/feedback on the matter. Sorry if > this one has come up before and I've not seen the thread. Have you read the JSON RFC? http://www.ietf.org/rfc/rfc4627.txt 4. Parsers A JSON parser transforms a JSON text into another representation. A JSON parser MUST accept all texts that conform to the JSON grammar. A...
    douglascrockford May 26, 2013
  • JavaScript, Java, and many other languages, were developed at a time when Unicode was going to be a 16-bit character set. Unicode later grew into a 21-bit character set. JSON took its representation of strings from JavaScript.
    douglascrockford Apr 7, 2013
  • From RFC 4672 http://www.ietf.org/rfc/rfc4627.txt?number=4627 To escape an extended character that is not in the Basic Multilingual Plane, the character is represented as a twelve-character sequence, encoding the UTF-16 surrogate pair. So, for example, a string containing only the G clef character (U+1D11E) may be represented as "\uD834\uDD1E".
    douglascrockford Apr 7, 2013