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; former steering group member) Yes

Yes ()
No email
send info

(Allison Mankin; former steering group member) No Objection

No Objection (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; former steering group member) No Objection

No Objection (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

(Bill Fenner; former steering group member) No Objection

No Objection ()
No email
send info

(Brian Carpenter; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Margaret Cullen; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Sam Hartman; former steering group member) No Objection

No Objection (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.

(Ted Hardie; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info