- From: Anders Rundgren <anders.rundgren@telia.com>
- Date: Sun, 20 Oct 2013 08:30:26 +0200
- To: sysapps <public-sysapps@w3.org>
Hi All, When I started "bombarding" the list with SE-related information in spite of the fact that the SE API effort wasn't started, one of the comments were that I didn't specify an SE API, but an SE Architecture. This is entirely correct and is so "by design". Is then the W3C SE API "neutral" with respect to SE architecture? No, it is about as bound to an architecture as my SKS/KeyGen2 project. A difference is that the W3C SE API leaves 7816/GP interoperability issues to the users to sort out while SKS/KeyGen2 is defined down to the bit-level. In essence, the W3C SE API brings out the "smart card middleware enigma" to web where an "ATR" string is supposed to trigger the right operations. I don't think this will scale particularly well. IMO an SE for the web must be considerably "profiled" in order to be useful. One might let the market forces do this but then we can have no idea of the outcome of the SE API. I would consider a GP profile. Anders
Received on Sunday, 20 October 2013 06:30:56 UTC