Re: Service Discovery and Sensor APIs: Demo of Webinos Service Discovery and Sensor APIs

Hi Claes,

Very cool. It works great. I would like to see this approach be applicable
in general to device APIs. As an option for exposing a service/application
to other devices on a home network, it is exactly what I had in mind per my
comments during the recent Web and TV IG meeting (see my email
http://lists.w3.org/Archives/Public/public-web-and-tv/2011Sep/0099.html,
option "3" that I mention).

As I understand it, on the discovering/accessing client side, there are no
browser requirements at all, as this operates purely over REST. I like that
- it makes it very easy to integrate to, with zero client-side requirements
other than REST and a JavaScript API to invoke the REST services (if needed,
so make it easier for the developer).

On the side of the discovered service (in this case a sensor bridge
service), if this is provided by a Web application, there needs to be the
ability to access the sensor data (what we are working on in DAP so far, and
what you showed in the Webinos API), but also the ability to advertise this
service to other devices. That advertisement aspect was one of the gaps
identified in the Web and TV IG meeting.

Thanks,
Bryan Sullivan

On Wed, Oct 5, 2011 at 6:47 AM, Nilsson, Claes1 <
Claes1.Nilsson@sonyericsson.com> wrote:

> Hi,****
>
> ** **
>
> I have created a simple demo that finds and displays the values of sensors
> in the current device as well in another wifi connected device. It
> implements the Webinos Service Discovery API,
> http://dev.webinos.org/specifications/draft/servicediscovery.html, and the
> Webinos Sensor API,
> http://dev.webinos.org/specifications/draft/sensors.html, ****
>
> ** **
>
> It works for Android 2.2 and later.****
>
> ** **
>
> The demo is here: http://www.semcsensors.appspot.com/ . The implementation
> of the Webinos Discovery and Sensor APIs use a simple REST API towards a
> local web server that provides access to the Android sensors . You need to
> download, install and start the local server. Link to this server is on the
> demo application page. ****
>
> ** **
>
> To get access to sensors on another Android device set this other device as
> a WiFi hotspot and connect to this device with WiFi from the device running
> the demo application. Then you will get a list of both the internal sensors
> and sensors on the other device. Note that the internal web server must be
> running on this other device as well.****
>
> ** **
>
> You can also run the demo application in your PC and connect with WiFi to
> an Android device and get access to the sensors on this device.****
>
> ** **
>
> By some reason you have to reload the demo application page after loading
> it the first time. ****
>
> ** **
>
> *Note *that this demo uses the Webinos sensor API and it displays the
> values of all sensors it finds in the Android device, including the
> accelerometer and compass values. This does not mean that I am convinced
> that the final version of the sensor API should provide access to
> accelerometer and compass. Access to these sensors are covered by the W3C
> Device Orientation API and we should probably not duplicate this
> functionality. However, I decided for demo purposes to include all Android
> sensors to show the general principle.****
>
> ** **
>
> Best regards****
>
>   Claes****
>
> ** **
>
> ** **
>
> [image: cid:3333625383_1036728]
>
> *Claes Nilsson M.Sc.E.E*
> Master Engineer, Research
> Technology Research - Advanced Application Lab
> *
> Sony Ericsson Mobile Communications*
>  Phone:  +46 10 80 15178
> Mobile: +46 705 56 68 78
> Switchboard: +46 10 80 00000
> E-Mail:* **mailto:claes1.nilsson@sonyericsson.com*<claes1.nilsson@sonyericsson.com>
> * *
> Visiting Address; Nya Vattentornet
> SE-221 88 LUND,
> Sweden ****
>
> *Disclaimer:
> *The information in this e-mail is confidential and may be legally
> privileged. It is intended solely for the named recipient(s) and access to
> this e-mail by anyone else is unauthorized. The views are those of the
> sender and not necessarily the views of Sony Ericsson and Sony Ericsson
> accepts no responsibility or liability whatsoever or howsoever arising in
> connection with this e-mail.Any attachment(s) to this message has been
> checked for viruses, but please rely on your own virus checker and
> procedures. If you contact us by e-mail, we will store your name and address
> to facilitate communications. If you are not the intended recipient, please
> inform the sender by replying this transmission and delete the e-mail and
> any copies of it without disclosing it.****
>
>  ****
>
> ** **
>



-- 

Thanks,
Bryan Sullivan