Re: ISSUE-14: Gathering requirements [System Info & Events]

On 5.10.2009 15.46, "ext Nilsson, Claes1" <>
> 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.

I think the operative word here is definitely "sensors", but thinking about
it, I would keep APIs related to system information and related events
separate from sensor input. I know that the lines tend to blur there, and I
have certainly had many debates as to whether the battery charge indicator
is a "sensor" just as an accelerometer (to give just a quick example). It
depends on your view of the world, I guess. :-)

There's a start of a thread about sensors [1], and I know Robin cautiously
opined [2] earlier that such would fit under System Information and Events.
This could be the beginning of an interesting (and long, and maybe
unnecessary) philosophical discussion, but in practical terms I'm simply
concerned about lumping sensors with system events. From a developer's point
of view a dedicated API for sensor data would probably be more palatable.

The argument for "universality" in API structure applies here as well as
with system events, of course.



Received on Monday, 5 October 2009 13:01:02 UTC