[1] [CITE[Introducing JSON]] > [CODE[JSON]] (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language. ([[名無しさん]]) [2] ''Semantic Interpretation for Speech Recognition (SISR) Version 1.0'' ([[名無しさん]] [WEAK[2006-01-19 03:31:05 +00:00]]) [3] [[RFC 4627]] ([[名無しさん]] [WEAK[2006-07-29 03:38:48 +00:00]]) [4] >>3 明記されていないけど [[BOM]] は使えないということでおk? ([[名無しさん]]) [5] 不適合文書の扱いも明記されていないけど、構文解析器は不適合も処理して'''構わない'''ことになっているから、 適当に理解するなりはじくなりでおk? ([[名無しさん]]) [6] [[サロゲート・ペア]]の片割れだけが escape されている場合は >>5? ([[名無しさん]]) [7] [CITE@ja-JP[Matzにっき(2007-04-16)]] ([[Yukihiro -matz- Matsumoto]] 著, [CODE[2007-04-23 23:58:26 +09:00]] 版) ([[名無しさん]] [WEAK[2007-05-05 03:25:51 +00:00]]) [8] [CITE@en[JSONLint - The JSON Validator.]] ([TIME[2008-06-22 12:32:25 +09:00]] 版) [9] [CITE[Re: Native JSON parsing API]] ([[Henri Sivonen]] 著, [TIME[2008-06-16 06:12:12 +09:00]] 版) > The JSON parsers I've used in non-browser contexts have been Draconian and incompatible with existing content such as output from del.icio.us, which can contain escaped single quotes, which isn't allowed in proper JSON. [10] [CITE[JSON Serialization (was Re: ES4 draft: Name)]] ([TIME[2008-04-01 12:34:49 +09:00]] 版) [11] [CITE[Re: Native JSON parsing API]] ([[Maciej Stachowiak ]] 著, [TIME[2008-06-14 08:43:00 +09:00]] 版) >Native JSON parsing is being considered for the next versions of ECMAScript (the 3.1 and 4 versions). It seems like a better fit there than in HTML5. If it ends up not being added to ECMAScript, I would propose it as a standalone spec for the W3C Web Apps WG.