Hello,

I'll break in for Tom and answer some of your questions..

| 3. If availability of and applet equals the USB HID capability, do you have unadvertised access to the button from JavaCard environment (or you use the javacard chip from the overall device controller? Basically, how it works.)

In mode 1 and 2 (not 81 and 82) an applet can access the state of the touch button, but it requires JCOP tools from NXP. The state of the button can be found with an operation like: IOControlX.getIO(IOControlX.IOID_P3)
It's a two-chip design with another chip driving the USB interface and the touch button.

| 4. Where is the APDU documentation for the two applets (other than NDEF public part)

We don't have any APDU documentation as such, but..
The NDEF applet only supports getting the OTP where there is one command to "select" the CC file (00 a4 00 0c 02 e1 03) or NDEF file (00 a4 00 0c 02 e1 04)
and then ins b0 to fetch the selected file.

for the YubiKey applet there are 4 commands:
ins 0x01 is a YubiKey API request (as used by the yubico personalization tools) with command in p1
ins 0x02 is a request for an OTP with slot in p1 (zero indexed)
ins 0x03 is a YubiKey status request
ins 0x04 is a request for NDEF (only used by the NDEF applet)

/klas

exps - No, we're not allowed to redistribute that.
for a shareable interface we've been throwing some stuff around internally with that in mind, nothing concrete yet.

/klas

What should be done to facilitate this process ? Needless to say I'm extremely excited about this possibility. Any of you @FOSDEM next weekend?