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


I think we need to consider also the contactless communication devices 
and their properties and APIs(NFC reader/tag, RFID reader/tag, etc). 

•MUST enable listing contactless communication devices (NFC, RFID) and their properties; 

Best Regards, 

--- Jonathan Jeon 

-----Original Message-----
From: [] On Behalf Of David Rogers
Sent: Wednesday, October 07, 2009 12:36 AM
To: Nilsson, Claes1; Tran, Dzung D;;;
Subject: RE: ISSUE-14: Gathering requirements [System Info & Events]


I have to say that from a personal perspective I agree, although then we could get into an academic argument about what if we had a USB API and a sensor was connected via USB (but I won't go there).

The question remains as to whether we should consider the subject of a sensors API as in-charter. Having re-read the charter, at the moment, I would say no. With the existing API proposals we have on the table I think we have a large amount of work and scope creep could be dangerous, taking apart any other potential IPR concerns.

Perhaps there is scope to start a separate discussion about the whole subject of transducers, not just sensors, With a view to re-chartering once there is something on the table (perhaps within the next year)? I wonder if the SCADA / PLC community would be interested in that part too?


Director of External Relations, OMTP

-----Original Message-----
From: [] On Behalf Of Nilsson, Claes1
Sent: 06 October 2009 09:44
To: 'Tran, Dzung D';;;
Subject: RE: ISSUE-14: Gathering requirements [System Info & Events]

Thanks Jere for pointing at the earlier threads about sensors.

I agree that it will be difficult to specify a unique API for each type of sensor and that some kind of "generic" sensor API makes sense. That was what I meant by "universality".


-----Original Message-----
From: Tran, Dzung D [] 
Sent: måndag den 5 oktober 2009 18:34
To:; Nilsson, Claes1;;
Subject: RE: ISSUE-14: Gathering requirements [System Info & Events]

It would be difficult to cover all the sensors ever made here, since new sensors come out all the time. Also, Geolocation is already a separate API and I consider Geolocation (GPS) is a sensor. I don't think it makes sense to have an API for each of type of sensor. 

Maybe a separate overall sensor APIs makes sense?

-----Original Message-----
From: [] 
Sent: Monday, October 05, 2009 06:00 AM
Cc: Tran, Dzung D;
Subject: 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 Wednesday, 7 October 2009 15:52:49 UTC