- From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
- Date: Mon, 5 Oct 2009 14:46:50 +0200
- To: 'Robin Berjon' <robin@robineko.com>, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
- CC: "Tran, Dzung D" <dzung.d.tran@intel.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Hi, I don't know if I am walking out of scope but I am considering "Personal Metrics" within training and healthcare. For example we have personal pulse watches, blood sugar sensors and blood pressure sensors. Web application access to measurement data from that type of devices, either "built in" or communicating with the device is needed. I guess that we can't predict all types of information that we need to access so some kind of "universality" would be useful within this context. Regards Claes -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Robin Berjon Sent: måndag den 5 oktober 2009 12:58 To: JOSE MANUEL CANTERA FONSECA Cc: Tran, Dzung D; public-device-apis@w3.org Subject: Re: ISSUE-14: Gathering requirements [System Info & Events] Hi Jose, On Oct 5, 2009, at 12:55 , JOSE MANUEL CANTERA FONSECA wrote: > I was referring to other kind of extensibility :) not to the fact > that Javascript is extensible by definition. > > I would rewrite the requirement as "universality", i.e. the API > should allow to access system information without requiring to > define new interfaces or operations or modifying existing ones ... Can you back this up with use cases and examples of what different approaches would look like? I think it would make the case clearer. -- Robin Berjon robineko - setting new standards http://robineko.com/
Received on Monday, 5 October 2009 12:47:25 UTC