- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Jun 2010 06:42:08 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9939
Gabriel Klein <gabriel.public.3@nuage.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gabriel.public.3@nuage.ch
--- Comment #1 from Gabriel Klein <gabriel.public.3@nuage.ch> 2010-06-17 06:42:08 ---
(details)
I see a demand for kind of "WebDevices".
What is my definition of WebDevices?
A webdevice is a device specific for a (or multiple) website.
Goal?
The goal is to allow manufacturer to create a specific device (or program) that
interact with a (or multiple) website without the need of installing drivers,
extra-security, etc.
Some example:
>> "Sign a URL" and a device.
This device once inserted can sign url with a specific id, timestamp.
Example: "banking access card". I insert my usb banking access card, enter a
password on this card, and it will start to sign all calls that come from my
bank. (with a "accept/deny" on the access card.)
>> Generate a one-time token
http://www.yubico.com/products/yubikey/
>> Share information with a website.
http://www.poken.com
When you "poken" with another poken, the information of the event is sent to a
website.
What some people are doing now?
(here are what some people are doing)
>> Creating a custom drivers
You need to install a driver on the operating system.
>> Generate a virtual usb keyboard.
When you "act" on the device, it "types" a list of characters. It might be a
token or a url.
>> Generate an html file.
We generate an html file that send the information when opened.
>> Have a java/other applet
This signed applet will have restricted access to the device.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 17 June 2010 06:42:10 UTC