The Technical workgroup of the OpenCard Consortium has decided in its
Chicago meeting
held on May, 11th,

that T=0 handling as specified in ISO 7816-4 Annex A is the responsibility
of the CardTerminal.
This means that CardTerminal implementers who support T=0 cards should
implement this function.
When CardTerminal.internalSendAPDU() is called and a CommandAPDU must be
mapped onto
more than one TPDU this should be done in the terminal.

Ambiguities of the get response class byte should be dealt with in the
CardTerminal.

Probably the consortium will provide utility classes in the future that
help to implement
the APDU -> TPDU mapping as specified by ISO.

Peter Bendel, Smartcard Solutions,       Tel.: +49-7031-16-4650, Fax -4888
Dept. 4969, Bldg. 7103-01, Room 01-109        Lotus Notes:  bed@ibmde
IBM Pervasive Computing Division         Internet: [EMAIL PROTECTED]

Please visit the OpenCard Framework's homepage at http://www.opencard.org


Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
access to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.

Reply via email to