(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.

Some features (optionnal)

>> You insert the web-device.
The browser open a specific website.

>> Events based
In javascript I write a code similar to
callback = {some code}
device = findDevice(...);
device.startListening(callback);

Every time I have an event on the device. (Example: I press the button of the device). I receive the information of the event.

>> Call based
device.call("signUrl");
This call will call a "function" on the device with a parameter "signUrl" and return a rest formated result.

Note:
The referer is sent to all calls that are made on the device.
So we can "verify" that an application (we hope the browser) sent the referer.

<device> is intended for things like cameras.

What you're describing sounds much more cutting-edge, and probably isn't appropriate for standardisation yet — we should experiment with it first. I recommend following the steps described here:

http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F