Find JSRs
Submit this Search


Ad Banner
 
 
 
 

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

Stage Access Start Finish
Final Release Download page 24 May, 2017  
Final Approval Ballot View results 18 Apr, 2017 01 May, 2017
Proposed Final Draft Download page 17 Mar, 2017  
Public Review Ballot View results 21 Feb, 2017 06 Mar, 2017
Public Review Download page 17 Jan, 2017 16 Feb, 2017
JSR Renewal Ballot View results 18 Oct, 2016 31 Oct, 2016
Early Draft Review Download page 03 Aug, 2015 02 Oct, 2015
JSR Review Ballot View results 09 Dec, 2014 22 Dec, 2014
JSR Review   25 Nov, 2014 08 Dec, 2014
Status: Active
JCP version in use: 2.10
Java Specification Participation Agreement version in use: 2.0


Description:
This JSR is to provide an update for the Java API for JSON Processing Specification.

Expert Group Transparency:
  Public Project Page
  Public Communications
  Issue Tracking

Team

Specification Leads
  Dmitry Kornilov Oracle
Expert Group
  Eugen Cepoi Sebastian Daschner IBM
: Nathan Mittlestat
  Werner Keil Mite Mitreski Oracle
: Roman Grigoriadi
  Oracle
: Lukas Jungmann
Oracle
: Dmitry Kornilov
Saly, Hendrik
: Hendrik Saly
  Samuraism Inc.
: Yusuke Yamamoto
Soto, Alex
Contributors
  Ozler, Hakan
: Hakan Ozler
Mark Struberg  

Updates to the Original JSR
The following updates have been made to the original proposal:

2016.10.13:
The Specification Lead has changed.

Specification Leads: Dmitry Kornilov

E-Mail Address: dmitry.kornilov@oracle.com

Telephone Number: +420 220 437 038

Fax Number: -

2015.07.14:
The schedule has been updated:
Q4 2015 Early Draft
Q1 2016 Public Review
Q3 2016 Proposed Final Draft
H1 2017 Final Release


Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Oracle

Name of Contact Person: Kin-man Chung

E-Mail Address: kinman.chung@oracle.com

Telephone Number: +1 408 276 7116

Fax Number: -


Specification Lead Member: Oracle Corporation

Specification Lead: Kin-man Chung

E-Mail Address: kinman.chung@oracle.com

Telephone Number: +1 408 276 7116

Fax Number: -


Initial Expert Group Membership:

TBD

Supporting this JSR:

Corporate:
IBM
JUGMK (Java User Group Macedonia)

Individuals:
Antonio Goncalves
Michael Remijan
Alex Soto
Yusuke Yamamoto
Werner Keil
Eugen Cepoi
Kito D. Mann
Mite Mitreski



Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to provide an update for the Java API for JSON Processing Specification (JSON-P).

There are 3 goals for this JSR.

* Support for JSON Pointer and JSON Patch

After the release of JSR 353, the specifications for JSON Pointer (http://tools.ietf.org/html/rfc6901) and JSON Patch (http://tools.ietf.org/html/rfc6902) have been released. This JSR will update JSON-P to provide support for these specifications.

* Add editing/transformation operations to JSON object model

The current JSON object model provides immutable JSON objects and arrays. It is useful to provide editing or transformation functionalities to the basic JSON processing.

For a JSON object, an operation will be added to remove a name/value pair from the object. For a JSON array, operations will be added to insert, replace, or remove an entry of the array.

The builder pattern will be used to handle these operations: a builder is created with the initial JSON object or array, the operations are carried out by the builder, and the edited object or array is finally converted to an immutable JSON object or array.

* Update the API to work with Java SE 8

Queries on JSON object model are currently possible, using Java SE 8's stream operations and lambda expressions. However, to make them truly useful and convenient, there is a need for Collectors that return JSON objects or arrays instead of Maps or Lists. This JSR will define some common and useful Collectors.

It may also be useful to turn JSON parser events into a stream of events, so that SE 8's stream operations can be used.

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

This specification is targeted for the Java SE 8 or higher and Java EE 8 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 8 platform.

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

See 2.1 above.

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

See 2.1 above.

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

Standard JSON format (http://json.org)
See 2.1 above for JSON Pointer and JSON Patch

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

javax.json
javax.json.spi
javax.json.stream

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

No.

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

No.

2.10 Are there any internationalization or localization issues?

This JSR will use the I18N support in Java SE.

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

No.

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

Q3 2014 Expert Group formed
Q1 2015 Early Draft
Q3 2015 Public Review
Q4 2015 Proposed Final Draft
Q3 2016 Final Release

2.13 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.14 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:

The http://java.net/projects/json-processing-spec project site will be used to track all issues and disseminate information on the progress of the JSR.

- 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?

The http://java.net/projects/json-processing-spec project users list (users@json-processing-spec.java.net) is used for this purpose.

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

The http://java.net/projects/json-processing-spec project users list (users@json-processing-spec.java.net) is used for this purpose.

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

Yes, at JavaOne.

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

Yes, the RI will be developed as an open java.net project. The TCK is not open source.

- 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 of use are those of java.net: http://www.java.net/javanet-web-site-terms-use

- What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.

The publicly-accessible Issue list is available at http://java.net/jira/browse/JSON_PROCESSING_SPEC

- What is the mechanism for the public to provide feedback on your JSR?

The public can provide feedback on the JSR by means of the users list.

- Where is the publicly-accessible document archive for your Expert Group?

The Expert Group's publicly readable mailing list will be archived at the projects java.net site, http://java.net/projects/json-processing-spec

- 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.

- Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?

Updates on the JSR will be made available on the project site, http://java.net/projects/json-processing-spec, and by means of the users list for the project.

- Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?

The formation of Adopt-a-JSR groups to provide technical feedback for JSON-P is encouraged and supported.

2.15 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 8 TCK.

2.16 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).

N/A

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

No license changes from the previous JSR (JSR-353) are planned.

Java API for JSON Processing 1.1 specification license

RI license

    Commercial use:
  1. The RI will be available for commercial use under the CDDL 1.1 open source license, the GPLv2 with Classpath Exception open source license, or this license.

  2. Non-Commercial use

    The RI will be available for non-Commercial use under the CDDL 1.1 open source license or the GPLv2 with Classpath Exception open source license.

TCK license

  1. Commercial use

    The Java EE 8 TCK will be available for commercial use under this TCK license.

  2. Non-Commercial use

    As required by the Java Specification Participation Agreement (JSPA), the TCK will be licensed at no charge without support to qualified not-for-profit. The Compatibility Testing Scholarship Program will verify such qualification. Support may also be provided at no charge with approval of the scholarship board. For more information, please refer to: http://www.oracle.com/technetwork/java/index-137188.html

2.18 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 a publicly readable alias. The public will have an alias on which to provide feedback and discuss issues related to the JSR. There will also be a publicly accessible JIRA and document archive. (See also 2.19 and 2.20 below.)

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

https://java.net/jira/browse/JSON_PROCESSING_SPEC

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

http://java.net/projects/json-processing-spec/downloads





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.

JSR 353: Java API for JSON Processing
http://jcp.org/en/jsr/detail?id=353

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

These specifications will be the starting point for this work.