Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)  |  Nominations
JSRs: Java Specification Requests
JSR 353: JavaTM API for JSON Processing

Stage Access Start Finish
Final Release Download page 23 May, 2013  
Final Approval Ballot View results 26 Mar, 2013 08 Apr, 2013
Proposed Final Draft Download page 27 Feb, 2013  
Public Review Ballot View results 22 Jan, 2013 04 Feb, 2013
Public Review Download page 22 Dec, 2012 21 Jan, 2013
Early Draft Review Download page 07 Sep, 2012 07 Oct, 2012
Expert Group Formation   04 Jan, 2012 07 Jun, 2012
JSR Review Ballot View results 20 Dec, 2011 03 Jan, 2012
JSR Review   06 Dec, 2011 19 Dec, 2011
Status: Final
JCP version in use: 2.8
Java Specification Participation Agreement version in use: 2.0

The Java API for JSON Processing (JSON-P) JSR will develop a Java API to process (for e.g. parse, generate, transform and query) JSON.

Expert Group Transparency:
  Public Communications
  Issue Tracking


Specification Leads
  Jitendra Kotamraju Oracle
Expert Group
  Green Tea JUG
: wen shao
Christian Grobmeier Horstmann, Jorn
: Jörn Horstmann
  Werner Keil Oracle
: Jitendra Kotamraju
Red Hat
: Jay Balunas
  Red Hat
: Marius Bogoevici
Red Hat
: Jonathan Fuerth
Twitter, Inc.
: Yusuke Yamamoto

Updates to the Original JSR

The following information has been updated from the original proposal on the dates shown.


Specification Lead: Kin-man Chung

E-Mail Address:

Telephone Number: +1 408 276 7116

Fax Number: -


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Oracle

Name of Contact Person: Jitendra Kotamraju

E-Mail Address:

Telephone Number: +1 408 276 7298

Fax Number: +1 408 276 7191

Specification Lead: Jitendra Kotamraju

E-Mail Address:

Telephone Number: +1 408 276 7298

Fax Number: +1 408 276 7191

Initial Expert Group Membership:


Supporting this JSR:

Douglas Crockford

Section 2: Request

2.1 Please describe the proposed Specification:

JSON(JavaScript Object Notation) is a lightweight data-interchange format. Many popular web services use JSON format for invoking and returning the data. Currently Java applications use different implementation libraries to produce/consume JSON from the web services. Hence, there is a need to standardize a Java API for JSON so that applications that use JSON need not bundle the implementation libraries but use the API. Applications will be smaller in size and portable.

The goal of this specification is to develop such APIs to:
* Produce and consume JSON text in a streaming fashion(similar to StAX API for XML)
* Build a Java object model for JSON text using API classes(similar to DOM API for XML)

Non-goals of this specification include:
* Binding of JSON text to Java objects and vice versa.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

This JSR is targeted for Java SE 6 or higher and Java EE 7 or higher platforms.

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

This JSR will be available standalone. It is also targeted for inclusion in the Java EE 7 platform.

2.4 Should this JSR be voted on by both Executive Committees?

No. By the SE/EE EC only.

2.5 What need of the Java community will be addressed by the proposed specification?

See 2.1 above.

2.6 Why isn't this need met by existing specifications?

See 2.1 above.

2.7 Please give a short description of the underlying technology or technologies:

Standard JSON format

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)


2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?


2.10 Are there any security issues that cannot be addressed by the current security model?


2.11 Are there any internationalization or localization issues?

This specification uses the I18N support in Java SE

2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?


2.13 Please describe the anticipated schedule for the development of this specification.

Dec 2011 Expert Group formed
Q1 2012 Early Draft
Q2 2012 Public Review
Q3 2012 Final Release

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

The primary means of communication will be email, with conference calls and face-to-face meetings scheduled as needed.

2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:

json-processing-spec project site will be used to track all issues and disseminate information on the progress of the JSR. The Expert Group will conduct business on a publicly readable alias. A private alias will be used only for EG administrative matters, as needed.

- Is the schedule for the JSR publicly available, current, and updated regularly?

The schedule will be available on the project page for the JSR.

- Can the public read and/or write to a wiki for the JSR?

We'll use a public mailing list for comments.

- Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?

We'll track such discussions and respond to them on the public comment mailing list.

- Have you spoken at conferences and events about the JSR recently?

Yes, in JavaOne 2011.

- Are you using open-source processes for the development of the RI and/or the TCK?

Yes, the RI will be developed as a project.

- What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?

The terms will be available on the project page for the JSR.

- Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?

Yes, it will point to the project page for the JSR.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The RI and TCK will be delivered both standalone and as part of the Java EE 7 TCK.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Note that this information has been updated since this original proposal.

Specification license
RI license
TCK license

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.

The Expert Group will conduct business on mailing list which is publicly readable.

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?

A JIRA issue tracker for json-processing-spec project will be used for this purpose. The issue tracker URL is

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group.

Expert Group's publicly readable mailing list will be archived at

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

3.2 Explanation of how these items might be used as a starting point for the work.

Will understand the current needs surrounding JSON usage and its implementations, and build an agreed API