[Chandler-dev] Fwd: RFC 4627 on The application/json Media Type for JavaScript Object Notation (JSON)

[Lisa Dusseault]

I think it was probably Matt that first raved about JSON and had me look at it even before I got involved shepherding it through the last couple steps of IETF process.  It's pretty simple, and this document seems to cover the whole thing.  Anyway, it's now a standard, and could be useful for us here and there.   Lisa Begin forwarded message: From: rfc-editor@rfc-editor.org Date: July 28, 2006 5:41:31 PM PDT To: ietf-announce@ietf.org, [EMAIL PROTECTED] Cc: rfc-editor@rfc-editor.org Subject: RFC 4627 on The application/json Media Type for _javascript_ Object Notation (JSON) A new Request for Comments is now available in online RFC libraries.         RFC 4627         Title:      The application/json Media Type for                      _javascript_ Object Notation (JSON)          Author:     D. Crockford         Status:     Informational         Date:       July 2006         Mailbox:    [EMAIL PROTECTED]         Pages:      10         Characters: 16319         Updates/Obsoletes/SeeAlso:   None         I-D Tag:    draft-crockford-jsonorg-json-04.txt         URL:        http://www.rfc-editor.org/rfc/rfc4627.txt _javascript_ Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format.  It was derived from the ECMAScript Programming Language Standard.  JSON defines a small set of formatting rules for the portable representation of structured data.  This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community.  It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED].  Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED]. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body  help: ways_to_get_rfcs. For example:         To: [EMAIL PROTECTED]         Subject: getting rfcs         help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED].  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev