Hello,

David Corcoran wrote:
> I created a new 'Documents' page on the site that is a bit cleaner.
> Gemplus has released their GemCore and Oros documentation in PDF
> that I am distributing on the web site.  This is low-level
> documentation for communicating with Gemplus smartcard readers.

Thanks Dave. I just want to add that these documents are also
available from the Gemplus Developers' web site, i.e.:

        http://www.gemplus.com/developers

(click on "Development Tools" > "Documentation"). I would suggest
to put URLs on the MUSCLE page in order to benefit from up-to-date
future releases.

Also, the Gemplus GCR API should be available as Open Source in the
next weeks when it's ready for release (as annouced at the Gemplus
Developers Conference last week). It is not intended to be a competitor
to the OCF or PC/SC standards, but rather to provide legacy solutions
to our customers while our efforts are now switched to the support
of OCF and PC/SC (e.g., the GCR API is the only one to be portable on
really all platforms, including MSDOS, it also deals with memory cards
or contactless cards/readers, which is not yet the case of OCF or
PC/SC), or to help the community with design ideas in order to enhance
the two other middleware solutions.

Cheers,
Christophe.

 = How many Bell Labs Vice Presidents does it take to change a light =
 = bulb?                                                             =
 = That's proprietary information.  Answer available from AT&T on    =
 = payment of license fee (binary only). Of course, this license     =
 = applies only if you have AT&T light bulbs; if you have someone    =
 = elses light bulbs then you have to pay both their license fee     =
 = and ours.                                                         =
_
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************

Reply via email to