Re: Introduction of WebI2C and WebGPIO

On Mon, Oct 19, 2015 at 6:30 PM, Michael Koster
<michaeljohnkoster@gmail.com> wrote:
> Satoru san, Futomi san,
>
> I understand your goal of combining web programming with low latency. It will enable precise control of devices in many important use cases using highly reusable code and design patterns. I see a larger potential also.
>
> In the bigger picture, it seems very worthwhile to be able to expose machine interfaces using common HTML code. This could enable the interface of something like a thermostat or lighting control to be discovered, rendered and processed using today’s tools of DOM and Javascript using familiar programming models.
>
>  It also enables the integration of well known hypermedia controls to expose resources using the Web of Things interaction model through markup-based controls that can be processed by Javascript handlers to drive application state machines. In addition, a resource like Schema.org could be used to provide common semantics, again integrated using markup like microformats.
>
> So the web browser doesn’t always need to run on the device. The device can still be a server that publishes the rich HTML document which enables the WoT interaction model between it and application clients that may or may not have screens.
>
> Or if there is a suitable environment on the device, the script code may run directly on the hardware I/O.

+1 on this. If there was a standard like this, I would gladly use in
in WeIO (http://we-io.net) project. Currently we had to cook our own -
explained here: http://we-io.net/doc/jsAPI.html - that borrows lot of
things from Arduino syntax to put it directly in the DOM - notice
stuff like digitalWrite(20, LOW); commands directly in HTML.

BR,
Drasko

Received on Monday, 19 October 2015 18:54:48 UTC