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

Note: This ballot was opened for revision 04 and is now closed.

(Scott Hollenbeck) Yes

(Brian Carpenter) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) (was Discuss) No Objection

(Sam Hartman) No Objection

Comment (2006-03-14)
No email
send info
This really belongs in the application subtree not the text subtree.
It is my understanding that is already being dealt with.

(Russ Housley) No Objection

(David Kessens) No Objection

(Allison Mankin) No Objection

Comment (2006-03-16)
No email
send info
If for any action, it would be an Note to the RFC Editor, but this 
is mainly for the APP intellectual apparatus:

Out of curiosity - I'm surprised by RFC 20 being this doc's cite
for ASCII.  I see that Wikipedia includes this reference (also RFC 1345,
which was not yet made Historic, but maybe should be).  RFC 20 is very
short and clear - is it still an accurate* source for ASCII?

(Bert Wijnen) No Objection

Comment (2006-03-15)
No email
send info
I had to read quite a bit of the document before I realized that this document basically is just requesting a MIME-type registration and has good documentation to go with it first.

So I wondered if the title would be better changed to somethinge like:

   The application/json media Type for JavaScript Object Notation (JSON)

Bert