Yes, you are right Uwe, OCF can be used to implement the smart card reader service of J/XFS. But this will remain hidden from J/XFS users who will use in any case a non-OCF approach. Am I right or do you have new not yet published documentation on J/XFS I have not yet read? Otherwise, I agree also that the first choice when dealing with smart card access with Java should be OCF by default. However, it may happen that for specific industries in need of frameworks integrating in a uniform way different platform services besides smart card reader service, like it is the case with J/XFS, OPTF, STIP, etc., you may choose for uniformity purpose another approach than the OCF one to provide smart card reader service to the users of the framework. You may or may not then implement your industry specific framework using internally OCF, but this will remain invisible to the users of your industry specific framework. On workstations where program size does not matter too much I would recommend to use OCF in any case for such industry specific framework implementation. On dedicated embedded devices, I would be much less affirmative on this point, if the industry specific framework you intend to implement is the only API that will be provided to application programmers on these devices. Jean-Paul [EMAIL PROTECTED] on 10/17/99 11:15:49 PM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Jean-Paul Billon/US/BULL) Subject: [OCF] [OCF] Re: [OCF] OTA vs. OCF Let me please just correct one statement from Jean-Paul about J/XFS. It is correct that there are possibilities to use J/XFS without using OCF, but the recommended way is to use OCF and this is also outlines in the J/XFS document and the use of OCF will be part of the J/XFS reference implementation. I don't want to open up the discussion again, so I don't want to comment on any further conclusions that Jean-Paul is making, but OCF should be your first choice for ALL Smart Card access using Java, no matter if it is for general purpose or limited to financial services. Best regards Uwe Hansmann ([EMAIL PROTECTED]) IBM Pervasive Computing Secretary of the OpenCard Consortium and the Open Services Gateway Initiative IBM Boeblingen, Dept. 4969 / 71032-01 Schoenaicherstr. 220, D-71032 Boeblingen, Germany Tel.: +49-7031-16-2267 (Fax: -4888 ) Mobile: +49-171-5560661 http://www.opencard.org http://www.osgi.org http://www.ibm.com/pvc ---------------------- Forwarded by Uwe Hansmann/Germany/IBM on 18.10.99 08:10 --------------------------- [EMAIL PROTECTED] on 17.10.99 12:54:03 Please respond to [EMAIL PROTECTED] To: Kyusoon LEE <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] (bcc: Uwe Hansmann/Germany/IBM) Subject: [OCF] Re: [OCF] OTA vs. OCF OTA is a framework for EFT-POS terminals designed sometime ago by interPay. OTA provides both a C and a Forth-like API and is not intended to use OCF nor PC/SC which generally are not available on the EFT-POS devices. More generally, if OCF provides a generic Java API for smart card access on workstation and, in a near future, on small smartcard-enabled and Java-enabled devices, there exists other industry specific frameworks that do not use the same approach to provide a smart card access than OCF or PC/SC. Besides OTA, the most different approach can be found with J/XFS (www.jxfs.com). J/XFS is a very interesting framework that provides, among other APIs, a very simple and quite original API for smart card readers. In the way initiated by J/XFS, STIP (www.stipgroup.org) is a new attempt to provide a Java framework for small EFT-POS terminals. STIP will provide an API for smart card access that will be very similar to the J/XFS one. A white paper about STIP will be available in December. Another framework for financial application is OPTF from Visa. OPTF is a high level abstract framework that can be implemented on top of STIP or alternatively can use PC/SC or OCF. OCF is a very complete and sophisticated generic framework dedicated exclusively to smart card access and card services. For industry specific purpose where, like in the financial industry, the notion of card service is not very useful, and where platforms are dedicated to a specific purpose, it may be necessary to define frameworks intended to integrate many kinds of platform services, among which smart card reader service can be treated in a much more elementary way than it is done in OCF. This is why OTA, J/XFS, STIP, are not related to OCF. But if you intend to use smart cards on a workstation or even on an embedded device to provide some kind of generic service, like secure file service, crypto service, etc, OCF is presently the good and unique standard choice available with Java. Jean-Paul Billon Chairman STIP workgroup Director, Software Architecture Bull Smart cards and Terminals, Foster City, CA Kyusoon LEE <[EMAIL PROTECTED]> on 10/16/99 11:58:16 PM To: [EMAIL PROTECTED] cc: (bcc: Jean-Paul Billon/US/BULL) Subject: [OCF] OTA vs. OCF I am confused between open terminal architecture(OTA) and open card frame(OCF). what's the differences? anybody can tell me? -- LEE, Kyusoon --- > Visit the OpenCard web site at http://www.opencard.org/ for more > information on OpenCard---binaries, source code, documents. > This list is being archived at http://www.opencard.org/archive/opencard/ --- > Visit the OpenCard web site at http://www.opencard.org/ for more > information on OpenCard---binaries, source code, documents. > This list is being archived at http://www.opencard.org/archive/opencard/ --- > Visit the OpenCard web site at http://www.opencard.org/ for more > information on OpenCard---binaries, source code, documents. > This list is being archived at http://www.opencard.org/archive/opencard/ --- > Visit the OpenCard web site at http://www.opencard.org/ for more > information on OpenCard---binaries, source code, documents. > This list is being archived at http://www.opencard.org/archive/opencard/
