Re: Request for interested participants in an Health & Welness Web Apps W3C community group

Could it not be an idea to have these sensors speaking something like websockets 
or server-sent events? (see html5 communications section), rather than implementing 
yet another protocol of communication?

Unless I'm not quite understanding the proposal.

Regards,
Micheil Smith
--
BrandedCode.com

On 29 Jun 2011, at 11:09, Lopez de la Fuente, Jose Manrique wrote:

> Hello everybody,
> 
> First of all, I would like to thank Dominique for giving us the opportunity to present here an idea we have been working on during several months.
> 
> My name is Manrique Lopez and I have been involved in W3C Mobile Initiative in the past, and I am writing here as member of the Continua Health Alliance[1]. I hold the 2nd Vice-Chair of the Technical Working Group (TWG) and I am mostly involved in the Moblity Task Force inside the WG.
> 
> The TWG's mission is to evaluate existing standards against requirements, based on Use Cases, in order to identify gaps and take steps to reconcile. One of the Use Cases identified by the Mobility TF is related with using a mobile web application to get data from health and welness sensors. Data could come from different sources, protocols and transport layers, and nowadays there are several apps for getting the same data, or you need a native app. There is no standard way to manage this data from a web app, specially since most of the solutions are based on native apps (that communicate with external devices using Bluetooth, ANT+, NFC, etc.).
> 
> Based on the work done by W3C DAP WG we have identified that it could be possible to define an standard Health & Wellness Sensors Web API that could be used by web apps to get data from internal and external sensors (through different transport layers). It would be a similar approach that it has been done for W3C Geolocation API. 
> 
> Continua does not create/write standards or recommendations, but it provides guidelines based on existing standards to ensure a E2E ecosystem of interoperable providers, as it does suggesting IEEE 11073 data format for data transmission between devices. So we would need someone to define that API standard, and we have thought as W3C as the perfect umbrella for this task. There are some companies in Continua willing to participate on this, and Dominique has suggested us to communicate our approach to the W3C DAP WG, because it would be possible to create a W3C Community Group [2] to start working on it, and see who would be interested in participating from the already existing W3C DAP WG.
> 
> From Continua side, there are at least 4 or  5 companies willing not only to participate but also to work on open implementations of the API.
> 
> I hope you could find this proposal interesting, and we are open to any question, comment or suggestion you could provide.
> 
> Again, thank you very much and best regards,
> 
> [1] http://www.continuaalliance.org
> [2] http://www.w3.org/2010/12/community/summary
> 
> -- 
> JOSE MANRIQUE LOPEZ DE LA FUENTE
> Health & Well-being Innovation Lab Manager
> M: +34 670 889 257
> T: +34 94 641 60 66
> F: +34 94 431 82 86
> josemanrique.lopez@andago.com
> ANDAGO LABS
> Bizkaia Technology Park
> Kanala Bidea, Edif-103, 1º izq.
> E-48170, Zamudio, Bizkaia (Spain)
> www.andago.com
> 
> 
> AVISO LEGAL
> ANDAGO CONSULTING SL / ANDAGO INGENIERÍA, SL le informa que los datos facilitados por Ud. y utilizados para el envío de esta comunicación serán objeto de tratamiento automatizado o no en nuestros ficheros, con la finalidad de gestionar la agenda de contactos de nuestra empresa y para el envío de comunicaciones profesionales por cualquier medio electrónico o no. Vd. podrá en cualquier momento ejercer el derecho de acceso, rectificación, cancelación y oposición en los términos establecidos en la Ley Orgánica 15/1999. El responsable del tratamiento es ANDAGO CONSULTING SL / ANDAGO INGENIERIA SL, con domicilio en C/ ALCALDE ANGEL ARROYO, 10, 28904, Getafe (Madrid).
> El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigido únicamente al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
> DISCLAIMER
> The content of this communication and any attached information is confidential and exclusively for the use of the addressee. If you are not the addressee, we ask you to notify to the sender and do not pass its content to another person, and please be sure you destroy it.
> 
>

Received on Wednesday, 29 June 2011 11:45:43 UTC