Hi,
What about TCP/IP over ethernet?? That's an infrastructure just like
smartcards are an infrastructure... It's the applications that a
ubiquitous card/reader system would enable that are
important... and I daresay required befor smartcards become
ubiquitous
Applications can be as
David Corcoran wrote:
Hi, here is a bit that I wrote up to vent on my lack of standards in the
smartcard industry. Let me know if you agree or not.
(and a great deal more besides).
If Birmingham Aston University (UK) mounts it on their unrestricted
web site, see the paper on smart card
Hi,
what if we built a smartcard "environmental system", a kind of
"middleware", that deals on one side with the cards and on the other side
with the (host) applications? On the cards' side, it would handle all
the specifics of smartcards. On the application side, it would offer
the smartcard
Mahlzeit
Harald Vogt wrote:
On the application side, it would offer
the smartcard services on a much higher abstraction level.
Are you talking about OCF? www.opencard.org
Mahlzeit
endergone Zwiebeltuete
***
Linux Smart Card
hali,
Standardization efforts could concentrate on the middleware and its
interfaces (to the smartcard side and the application side). No need to
standardize every bit on the cards. These interfaces could even be
service independant such that new services could be introduced easily,
without
On Don, 18 Mai 2000, Matthias Bruestle wrote:
Mahlzeit
Harald Vogt wrote:
On the application side, it would offer
the smartcard services on a much higher abstraction level.
Are you talking about OCF? www.opencard.org
Not necessarily. OCF has a few drawbacks. It's Java-specific,
local
unsubscribe MUSCLE
end
Met de vriendelijke groeten,
Raymond.
Treaties are like roses and young girls -- they last while they last.
-- Charles DeGaulle
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the
