everyrfc.org 2024 著作権. ä¸è¨±è¤‡è£½ プライãƒã‚·ãƒ¼ãƒãƒªã‚·ãƒ¼
everyrfc.org
everyrfc.org 2024 著作権. ä¸è¨±è¤‡è£½ プライãƒã‚·ãƒ¼ãƒãƒªã‚·ãƒ¼
事実上最後ã®JSON仕様「RFC 8259ã€ã¨ã€ŒECMA-404 2nd Editonã€å…¬é–‹ã€‚UTF-8ã‚¨ãƒ³ã‚³ãƒ¼ãƒ‰å¿…é ˆã«
RESTful APIã®ãƒ‡ãƒ¼ã‚¿ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆãªã©ã§åºƒã使ã‚ã‚Œã¦ã„ã‚‹JSON。IETFã¯JSON仕様「RFC 8259ã€ã‚’発表。従æ¥ã®ä»•æ§˜ã‚’ブラッシュアップã—ã¤ã¤ECMAã®ä»•æ§˜ã¨ã®çµ±ä¸€ã‚‚実ç¾ã—ãŸã€äº‹å®Ÿä¸Šæœ€å¾Œã®JSON仕様ã«ãªã‚‹ã¨è¦‹ã‚‰ã‚Œã‚‹ã€‚ IETFã‹ã‚‰JSON（ジェイソン）ã®ä»•æ§˜ã‚’示ã—ãŸã€ŒRFC 8259ã€ï¼ˆThe JavaScript Object Notation (JSON) Data Interchange Format）ãŒå…¬é–‹ã•ã‚Œã¾ã—ãŸã€‚ IETFã«ãŠã‘ã‚‹JSON仕様ã¯ã€ã“ã‚Œã¾ã§ã€ŒRFC 7159ã€ãŒå‚ç…§ã•ã‚Œã¦ã„ã¾ã—ãŸãŒã€RFC 8259ã®å…¬é–‹ã«ã‚ˆã‚ŠRFC 7159ã¯å»ƒæ¢ï¼ˆObsolete）ã¨ãªã‚Šã¾ã—ãŸã€‚ RFC 8259ã¯ã€å¤šæ•°ã®å®Ÿè£…ã¨å分ãªé‹ç”¨å®Ÿç¸¾ã‚’ç©ã¿é‡ããŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆæ¨™æº–「STD 90ã€ã¨ã—ã¦ã‚‚å‚ç…§ã•ã‚Œã¾ã™ã€‚ ECMAã¨ã®çµ±ä¸€ã‚’実ç¾ã€‚事実上最後ã®JSON仕様ã«ãªã‚‹ã¨è¦‹ã‚‰ã‚Œã‚‹
RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Internet Engineering Task Force (IETF) T. Bray, Ed. Request for Comments: 7159 Google, Inc. Obsoletes: 4627, 7158 March 2014 Category: Standards Track ISSN: 2070-1721 The JavaScript Object Notation (JSON) Data Interchange Format Abstract JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Langu
RFC2616 is Dead
Hi, I’m Mark Nottingham. I usually write here about the Web, protocol design, HTTP, and Internet governance. Find out more. Comments? Let's talk on Mastodon. @mnot@techpolicy.social Saturday, 7 June 2014 HTTP Standards Web Don’t use RFC2616. Delete it from your hard drives, bookmarks, and burn (or responsibly recycle) any copies that are printed out. Since 1999, it has served as the definition of
RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
Internet Engineering Task Force (IETF) P. Saint-Andre Request for Comments: 6648 Cisco Systems, Inc. BCP: 178 D. Crocker Category: Best Current Practice Brandenburg InternetWorking ISSN: 2070-1721 M. Nottingham Rackspace June 2012 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols Abstract Historically, designers and implementers of application protocols have often disting
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
https://www.ietf.org/rfc/rfc4356.txt
{{#tags}}- {{label}}
{{/tags}}