Hello,
Michael Bender wrote:
>> If you still consider renaming the core package please follow the
>> RFC process that the Opencard Consortium has defined:
>> As Sun is a member of the Technical workgroup you can submit an RFP
>> that requests the renaming of opencard.core package to
>> opencard.whateveryoulike which is then voted by the consortium
>> members.
>
> OK I can do that. I wanted to get feedback from people on this list to
> see if such a change was even remotely palatable before I submitted
> the RFC.
>
> What do you all think?
Mike, we have talked a little about this in Chicago during the
last technical committee meeting. In fact, I think a majority
of the members would like to follow the current Java habits by
having two class hierarchy starting by opencard and opencardx
for respectively the core features and the optional extensions
(like what exists with java/javax or javacard/javacardx).
So for example we would have an opencard.terminal package for
core classes belonging to the CardTerminal layer and an
opencardx.terminal package for optional features such as
screen/keyboard interfaces etc.
In fact, from what I heard from the members (they will reply to
my message if I got it all wrong :-), a lot of people agree that:
- it would be nice (although those conventions did not exist at
the time the first opencard packages where named..)
- BUT it would break some code, people will have to adapt to the
new API, and
- we need *somebody* to do the work, I.e., issue the RFP and RFC,
and provide a port of the current framework implementation. Would
you be this person Mike?
What would be really nice is to provide not only a port of the
framework but also some kind of perl script that handles the job
more or less automatically for all CardTerminal/CardServices or
applications implementers out there.
My two eurocents..
Cheers,
Christophe.
= Bloody typical, they've gone back to metric without telling us. =
= -- Charlie, Department of Works (Brazil) =
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.
