W3C home > Mailing lists > Public > public-xg-ssn@w3.org > February 2012

Re: [via Web of Sensors Community Group]

From: Marcos Caceres <w3c@marcosc.com>
Date: Wed, 22 Feb 2012 19:39:42 +0000
To: Peter Waher <Peter.Waher@clayster.com>
Cc: Myriam Leggieri <myriam.leggieri@deri.org>, Arthur Barstow <art.barstow@nokia.com>, "public-sensorweb@w3.org" <public-sensorweb@w3.org>, "public-xg-ssn@w3.org WG" <public-xg-ssn@w3.org>, Manfred Hauswirth <manfred.hauswirth@deri.org>, Michael Hausenblas <michael.hausenblas@deri.org>
Message-ID: <7030370E9D6E4F8EB8F5631CAB7D3065@marcosc.com>


On Wednesday, February 22, 2012 at 6:25 PM, Peter Waher wrote:

>  
> When it comes to browser support for the semantic sensor networks, we have an interesting use case we would like to see realized: Consider IP-TV together with semantic home networks (for energy management, home automation, residential services, etc.)  
Out of interest, are there commercially available solutions of the above that are currently using semantic web technologies?   
> We work with both areas, but one problem that arises is this: How can the IP-TV system access and use sensors at home? Today, the sensor values have to travel from the sensors, through gateways to a centralized metering system, communicating with the IP-TV system, that then publishes the information to the user, a couple of meters away from the sensor. This, apart from inducing many items that could fail, also puts load on the network, and latency.  

Yes, it's annoying and overly complicated...   
> However, if the set-top-box (running a browser) would be able to access the gateway (through XHR), locally, or using HTML5 extensions, could access the SPARQL endpoint in the local network, and all data there, a better architecture and solution would be available. This of course leads to a whole series of security issues, some more or less delt with if HTTP/HTTPS and authentication is used, but anyway. Also the issue of service detection (or endpoint detection in networks).


So, questions I have: no browser natively supports SPARQL (or any Semantic Web technology, and they have no plans to do so), but browsers will soon support IndexedDB (experimental builds are already coming from Moz, Google, and MS)… would it make sense to explore using an IndexedDB solution? Also, browsers support JSON natively, so why not try to build something on that (and see where it breaks down for the particular use cases… whatever they might be)?   

Also, given the proliferation of UPNP and DLNA devices… would it not be worth while to look at exploiting those first?  

--  
Marcos Caceres
Received on Wednesday, 22 February 2012 19:40:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 22 February 2012 19:40:14 GMT