 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 268: JavaTM Smart Card I/O API
JCP version in use: 2.6 Java Specification Participation Agreement version in use: 2.0 Description: APIs for APDU based communication with Smart Cards Please direct comments on this JSR to the Spec Lead(s) Team
The following information has been updated from the original request. 2006.10.24: 2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.Sun will be licensing the JSR 268 binary under Sun's standard Binary Code License (BCL) at zero charge.Sun will license the JSR-268 TCK for a flat fee of $50 K. Sun will license the RI source code under the Java Research License at zero charge. Sun will license the RI source code under the Java Distribution License at zero charge for the source code and $50 K for the TCK.
2005.10.06: 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.This JSR will be delivered standalone. 2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.Sun will license the JSR 268 RI binary at zero charge. Sun will license the JSR-268 TCK for a flat fee of $50 K. In addition, qualified individuals and not for profit organizations will receive access to the TCK at no charge. Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Sun Microsystems, Inc. Name of Contact Person: Andreas Sterbenz E-Mail Address: Andreas.Sterbenz@sun.com Telephone Number: +1 408 276 7393 Fax Number: +1 408 276 7700 Specification Lead: Andreas Sterbenz E-Mail Address: Andreas.Sterbenz@sun.com Telephone Number: +1 408 276 7393 Fax Number: +1 408 276 7700 Initial Expert Group Membership: Sun Microsystems Supporting this JSR: Sun Microsystems Section 2: Request
2.1 Please describe the proposed Specification:Smart Cards, also called integrated circuit cards, are small computing devices that usually come in a credit card sized form factor. Server and PC applications interact with Smart Cards by exchanging APDUs (Application Protocol Data Units) with them. This JSR will define a Java API for such APDU based communication. The API will be designed to be compact but sufficiently complete to satisfy the majority of applications. We envision an API roughly equivalent in features to the resource manager in the PC/SC Workgroup specifications. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)J2SE 5.0 and later. 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.J2SE 2.4 Should this JSR be voted on by both Executive Committees?No 2.5 What need of the Java community will be addressed by the proposed specification?There is a huge number of Smart Cards in circulation today. This JSR will make it easier for Java applications to take advantage of their benefits, such as their security and portability features. 2.6 Why isn't this need met by existing specifications?There is no active J2SE specification addressing this problem space. There was a previous effort to create a javax.smartcard API. That effort predated the JCP. Some level of API was created, but there was no TCK. Work ceased on this initiative in 1998. We investigated reviving that API instead of launching a new JSR. However, the earlier API is not well aligned with current Java APIs and programming styles or the dominant PC/SC standard. We therefore believe that the needs of the Java Community are better served by defining a new API. 2.7 Please give a short description of the underlying technology or technologies:See 2.1 and 3.1 2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)javax.io.smartcard 2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.10 Are there any security issues that cannot be addressed by the current security model?No 2.11 Are there any internationalization or localization issues?No 2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?No 2.13 Please describe the anticipated schedule for the development of this specification.Expert group formation: Jan-Feb 2005 2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.Expert group business will be conducted via a mailing list. Conference calls will be scheduled if necessary. 2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.We will set up a public announcement mailing list or a discussion forum. 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.NOTE that this information has been updated from this original request.We plan to deliver and license the RI and TCK as part of the RI and TCK for Mustang. 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).N/A 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 from this original request.We plan to deliver and license the RI and TCK as part of the RI and TCK for Mustang. 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.ISO/IEC 7816, available at http://www.iso.org PC/SC Workgroup Specifications, available at http://www.pcscworkgroup.com/specifications/specdownload.php 3.2 Explanation of how these items might be used as a starting point for the work.These standards define the problem space. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
