List Info

Thread: RFC 4627 on The application/json Media Type for JavaScript Object Notation (JSON)
RFC 4627 on The application/json Media Type for JavaScript Object Notation (JSON)
user name
 2006-07-31 21:55:41 

  


  

    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:

Date: July 28, 2006 5:41:31 PM PDT
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:    crockford.com">douglascrockford.com
        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 IETF.ORG">IETF-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to RFC-EDITOR.ORG">rfc-infoRFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        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 RFC-EDITOR.ORG">RFC-ManagerRFC-EDITOR.ORG.  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.ORG">RFC-EDITORRFC-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
 


  

  
  
   
     
    

  

    RFC 4627 on The application/json Media
Type for JavaScript Object Notation
(JSON)
  


  

     user name

     2006-08-01 03:31:16
  


  

    
Huzzah!

This will be a real boon for client-side devs out there who
are 
currently dealing with brittle and finicky XML data in their
JavaScript 
code. Now they can point to an actual standards doc when
they're 
explaining to their bosses that they want to use something
else.


Matthew


Lisa Dusseault wrote:
> 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-editorrfc-editor.org
<mailto:rfc-editorrfc-editor.org>
>> *Date: *July 28, 2006 5:41:31 PM PDT
>> *To: *ietf-announceietf.org
<mailto:ietf-announceietf.org>, 
>> rfc-distrfc-editor.org <mailto:rfc-distrfc-editor.org>
>> *Cc: *rfc-editorrfc-editor.org
<mailto:rfc-editorrfc-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:    douglascrockford.com
<mailto:douglascrockford.com>
>>         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 IETF-REQUESTIETF.ORG 
>> <mailto:IETF-REQUESTIETF.ORG>.  Requests to
be
>> added to or deleted from the RFC-DIST distribution
list should
>> be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG 
>> <mailto:RFC-DIST-REQUESTRFC-EDITOR.ORG>.
>>
>> Details on obtaining RFCs via FTP or EMAIL may be
obtained by sending
>> an EMAIL message to rfc-infoRFC-EDITOR.ORG 
>> <mailto:rfc-infoRFC-EDITOR.ORG> with the
message body 
>>
>> help: ways_to_get_rfcs. For example:
>>
>>         To: rfc-infoRFC-EDITOR.ORG
<mailto:rfc-infoRFC-EDITOR.ORG>
>>         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
RFC-ManagerRFC-EDITOR.ORG 
>> <mailto:RFC-ManagerRFC-EDITOR.ORG>.  Unless
>> specifically noted otherwise on the RFC itself, all
RFCs are for
>> unlimited distribution.
>>
>> Submissions for Requests for Comments should be
sent to
>> RFC-EDITORRFC-EDITOR.ORG <mailto:RFC-EDITORRFC-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-Announceietf.org <mailto:IETF-Announceietf.org>
>> 
https://www1.ietf.org/mailman/listinfo/ietf-announce
> 
> 
>
------------------------------------------------------------
------------
> 
> _______________________________________________
> scooby-dev mailing list
> scooby-devlists.osafoundation.org
> http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev


  


  

    
  

  
  
   
     
    

  

    RFC 4627 on The application/json Media
Type for JavaScript Object Notation
(JSON)
  


  

     user name

     2006-08-01 03:31:16
  


  

    
Huzzah!

This will be a real boon for client-side devs out there who
are 
currently dealing with brittle and finicky XML data in their
JavaScript 
code. Now they can point to an actual standards doc when
they're 
explaining to their bosses that they want to use something
else.


Matthew


Lisa Dusseault wrote:
> 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-editorrfc-editor.org
<mailto:rfc-editorrfc-editor.org>
>> *Date: *July 28, 2006 5:41:31 PM PDT
>> *To: *ietf-announceietf.org
<mailto:ietf-announceietf.org>, 
>> rfc-distrfc-editor.org <mailto:rfc-distrfc-editor.org>
>> *Cc: *rfc-editorrfc-editor.org
<mailto:rfc-editorrfc-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:    douglascrockford.com
<mailto:douglascrockford.com>
>>         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 IETF-REQUESTIETF.ORG 
>> <mailto:IETF-REQUESTIETF.ORG>.  Requests to
be
>> added to or deleted from the RFC-DIST distribution
list should
>> be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG 
>> <mailto:RFC-DIST-REQUESTRFC-EDITOR.ORG>.
>>
>> Details on obtaining RFCs via FTP or EMAIL may be
obtained by sending
>> an EMAIL message to rfc-infoRFC-EDITOR.ORG 
>> <mailto:rfc-infoRFC-EDITOR.ORG> with the
message body 
>>
>> help: ways_to_get_rfcs. For example:
>>
>>         To: rfc-infoRFC-EDITOR.ORG
<mailto:rfc-infoRFC-EDITOR.ORG>
>>         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
RFC-ManagerRFC-EDITOR.ORG 
>> <mailto:RFC-ManagerRFC-EDITOR.ORG>.  Unless
>> specifically noted otherwise on the RFC itself, all
RFCs are for
>> unlimited distribution.
>>
>> Submissions for Requests for Comments should be
sent to
>> RFC-EDITORRFC-EDITOR.ORG <mailto:RFC-EDITORRFC-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-Announceietf.org <mailto:IETF-Announceietf.org>
>> 
https://www1.ietf.org/mailman/listinfo/ietf-announce
> 
> 
>
------------------------------------------------------------
------------
> 
> _______________________________________________
> scooby-dev mailing list
> scooby-devlists.osafoundation.org
> http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev

_______________________________________________
scooby-dev mailing list
scooby-devlists.osafoundation.org
http://lists.osafoundation.org/cgi-bin/mailman
/listinfo/scooby-dev


  


  

    
  

  
  
   
     
    






 [1-3]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )