Updates to the Original JSR
The following updates have been made to the original proposal:
2015年11月02日:
The Spec Lead representative changed to Dmitry Kornilov.
Specification Lead: Dmitry Kornilov, Oracle
E-Mail Address: dmitry.kornilov
Telephone Number: +420 220 437 038
Fax Number: -
2015年07月14日:
Original Java Specification Request (JSR)
Identification |
Request |
Contributions |
Additional Information
Section 1. Identification
Submitting Member: Oracle
Name of Contact Person: (削除) Martin Grebac (削除ここまで)
E-Mail Address: (削除) martin.grebac
Telephone Number: (削除) +420 221 438 700 (削除ここまで)
Fax Number: (削除) +420 221 438 700 (削除ここまで)
Specification Lead: (削除) Martin Grebac, Oracle (削除ここまで)
E-Mail Address: (削除) martin.grebac
Telephone Number: (削除) +420 221 438 700 (削除ここまで)
Fax Number: (削除) +420 221 438 700 (削除ここまで)
Specification Lead: Dmitry Kornilov, Oracle
E-Mail Address: dmitry.kornilov
Telephone Number: +420 220 437 038
Fax Number: -
Initial Expert Group Membership:
Oracle
Supporting this JSR:
Werner Keil (JSON-P EG Member, JSR 363 Spec Lead)
Red Hat
Kyung Koo Yoon, TmaxSoft
Section 2: Request
JSON has grown considerably as a portable means to represent objects and data. It is used by more and more systems and layers, ranging from web services to configuration data.
The recently established Java API for JSON Processing (JSON-P) specification defines a standard API for parsing and generating JSON data. The next logical step is to standardize a way to convert JSON into Java objects and vice versa. JSON-B will leverage JSON-P and provide a conversion layer above it.
JSON-B will be the standard binding layer for converting Java objects to/from JSON messages. A default mapping algorithm will be defined for converting existing Java classes to JSON. The default mappings can be customized through the use of Java annotations and will be leveraged by the JSON-B runtime to convert Java objects to/from JSON.
JSON-B will be useful to a number of the upper layers, such as JAX-RS. The requirements of these layers may be complex and include such features as bidirectional mappings and composite key support. Such requirements, as well as others that may be discussed, will be considered and incorporated as time permits.
As JAXB has been a successful platform for XML binding, JSON-B will have a similar feel. This will make it easier for JSON-B to be adopted by Java SE and Java EE developers.
This JSR is targeted for Java SE 7 or higher and Java EE 7 or higher platforms.
This JSR will work with Java EE 7 and will be targeted for inclusion in Java EE 8.
There is currently a need in JAX-RS to convert objects to/from JSON messages. The community is currently forced to do one of the following:
- Do the conversion themselves
- Use JAXB with libraries like Jettison to get a 'good enough' conversion.
- Use non-standard tools, resulting in non-portable applications.
Many services (Twitter, Google Geocoding API, etc) are offering data via JSON messages that Java developers need to interact with as Java objects. Some such as Twitter are even dropping the XML version of these APIs.
Java API for JSON Processing (JSON-P) JSR
- The above JSR provides a generic model to represent a JSON message. JSON-B will bind the JSON message to a real object domain model.
Java API for XML Binding (JAXB) JSR
The JSON databinding need is currently being addressed by the JAXB specification together with libraries that expose JSON messages via StAX APIs. However, this approach faces following problems:
- Some of the JAXB mapping concepts have no JSON equivalent: namespaces, substitution groups, etc. Problems can arise when these mappings are used to produce JSON messages.
- It is difficult to produce JSON messages with collections of size one. This is due to a difference in the way JSON and XML represent collections.
- The JAXB approach assumes that the XML and JSON messages have same general structure and names.
JSON-B will integrate with Java API for JSON Processing (JSON-P).
javax.json.bind
No.
No.
This specification uses the I18N support in Java SE.
No.
Q3 2014 Expert Group formed
Q1 2015 Early Draft
Q3 2015 Public Review
Q4 2015 Proposed Final Draft
Q3 2016 Final Release
The primary means of communication will be email, with weekly conference calls and a possibility of face-to-face meetings.
- Is the schedule for the JSR publicly available, current, and updated regularly?
Schedule will be available on the java.net project page for the JSR: https://java.net/projects/jsonb-spec/
- Can the public read and/or write to a wiki for the JSR?
Public mailing list will be used for comments (users@jsonb-spec.java.net)
- Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
Public mailing list will be used for comments (users@jsonb-spec.java.net)
- Have you spoken at conferences and events about the JSR recently?
No
- Are you using open-source processes for the development of the RI and/or the TCK?
Yes, the RI will be done under open source EclipseLink project, http://eclipselink.org. 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?
Terms of use 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.
- JIRA is part of the JSR java.net project, and will be linked from there; https://java.net/jira/browse/JSONB_SPEC
- What is the mechanism for the public to provide feedback on your JSR?
Public mailing list will be used for comments (users@jsonb-spec.java.net)
- Where is the publicly-accessible document archive for your Expert Group?
At the java.net 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.
- Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?
Public user list and project site will be used to provide updates on the JSR.
- 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)?
Technical feedback for individual parts of the JSR is welcome.
The RI and TCK will be provided stand-alone, and will be included in the Java EE 8 RI and TCK.
N/A
RI license
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 RI license.
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
The TCK will be available for commercial use under this TCK license.
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
JSR java.net project will contain publicly available mailing lists, archives, and document download areas. For more details, please refer to the transparency section above.
https://java.net/jira/browse/JSONB_SPEC/ URL will be also provided at the JSR java.net project page. JIRA use is described in JIRA documentation https://confluence.atlassian.com/display/JIRA/Creating+an+Issue
https://java.net/projects/jsonb-spec/downloads. The URL will also be linked from the JSR project web page.
Section 3: Contributions
JSON - http://json.org/ Open Source Object-to-JSON Implementations:
- EclipseLink MOXy (http://www.eclipse.org/eclipselink/moxy.php)
- Jackson (http://jackson.codehaus.org/)
- Google GSON (http://code.google.com/p/google-gson/)
- XStream (http://xstream.codehaus.org/)
- Genson (http://code.google.com/p/genson/)
JSON-P (JSR-353) -
There is now enough industry experience with object-to-JSON binding that the lessons learned from current implementations can be leveraged to form a Java standard that will add value to the Java stack.
Section 4: Additional Information (Optional)
There are several open source object-to-JSON binding solutions available today. The leads of these projects will be invited to join this expert group.