Re: webGPIO and webI2C implementations progress and introduction

This work seems interesting in the context of the Web Bluetooth API being
developed by the Web Bluetooth CG and the Serial and WebUSB APIs being
developed in the WICG. Will you be attending our F2F in Fukuoka next month?
[image: Google Logo]
Reilly Grant
Software Engineer
reillyg@google.com
Google Chrome


On Sun, Aug 18, 2019 at 6:33 PM sa-takagi@kddi.com <sa-takagi@kddi.com>
wrote:

> Hi Devices and Sensors WG member,
>
> I am working to make board computers convenient to use from web browsers
> mainly for STEM training materials as a member of open source communities.
> I imagine that our activities described below may be related to this
> Devices and Sensors WG.
> I'm happy if I have the opportunity to exchange opinions with you at TPAC
> 2019.
>
> For several years, Browsers and Robotics Community Group at W3C is
> studying specifications that allow the board computer's pins (GPIO and I2C,
> SPI in the future) to be operated directly from browsers, named WebGPIO*1
> and WebI2C*1. While rough referencing webMIDI etc.
> *1: https://github.com/browserobo/WebGPIO
> *2: https://github.com/browserobo/WebI2C
>
> And, CHIRIMEN community (outside W3C) is implementing these specifications
> and building training materials that package it.
> There are implementations for Raspberry Pi3*3, micro:bit*4, and mbed*5
> board computers. For Raspberry Pi3, webApps running on browsers on the
> Raspberry Pi3 controls the pins directly, while for the others, browsers
> connected via web Bluetooth controls the pins on the board computers.
>
> *3: https://github.com/chirimen-oh/chirimen-raspi3
> *4: https://github.com/chirimen-oh/chirimen-micro-bit
> *5: https://github.com/chirimen-oh/chirimen-TY51822r3
>
> This training materials are also used in multiple activities to train
> young engineers related to IoT.
>
> Regards
>
> Satoru Takagi
> AC Rep. KDDI
>
>
>
>