W3C home > Mailing lists > Public > public-webscreens@w3.org > October 2015

RE: Proposals for new deliverables

From: BELLESSORT Romain <Romain.Bellessort@crf.canon.fr>
Date: Thu, 8 Oct 2015 08:32:33 +0000
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "public-webscreens@w3.org" <public-webscreens@w3.org>
CC: FABLET Youenn <Youenn.Fablet@crf.canon.fr>
Message-ID: <dfd90663-ce53-428f-a2bb-774130e556b3@Antiope.crf.canon.fr>
Hi Anssi,

Sorry for this late response. At last TPAC, a session was organized about "startSession("WoT devices")" [1]. Interesting outcomes were delivered during this session, including:
- Tatsuya Igarashi (Sony) made a presentation [2] showing that an API somehow similar to the Presentation API could be used as an alternative to the Network Service Discovery API (NSD API); 
- Saki Honma (NTT) made a demo [3] in which a web app relying on an extended Presentation API was able to interact with a camera through a node.js device driver; said API allowed web app to connect to said driver in order to exchange messages with it, said driver then exchanging other messages with the camera in order to perform requested operations.

As illustrated by past work on NSD API (which is no more progressing due to security concerns) and recent activity in the WoT IG, we believe that there is a need for an API allowing a web app to interact with remote devices. Above outcomes as well as Louay Bassbouss proposal for a Thing API [4] show that extending the Presentation API to non-screen devices may offer an interesting solution. In particular, usage of an intermediary driver could avoid having a direct connection between client web app and remote device, an issue that plagued NSD API. Designing such an API would of course present some challenges (e.g. what argument should be provided to start a session), but we feel that it would be worth investigating by this CG.

Regards,

Romain.

[1] https://www.w3.org/wiki/TPAC2014/SessionIdeas#startSession.28.22WoT_devices.22.29	
[2] https://www.w3.org/wiki/images/1/1d/StartSession%28WoT_Devices%29_TPAC2014.pdf
[3] https://www.w3.org/wiki/images/2/20/Presentaionapi_for_nonscreen_devices.pdf
[4] https://lists.w3.org/Archives/Public/public-wot-ig/2015Sep/0057.html

> -----Original Message-----
> From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com]
> Sent: mercredi 22 avril 2015 12:55
> To: public-webscreens@w3.org
> Subject: Proposals for new deliverables
> 
> Hi All,
> 
> There's quite some overlap in the Second Screen Presentation Community
> Group [1] and Working Group [2] participation, which is great.
> 
> While the active discussion is happening in the WG [2] now as we advance
> the Presentation API on the standards track, this Community Group is still the
> place for experimenting with features that are out of scope for the Working
> Group.
> 
> All - please let me know if you have proposals in mind you'd like to see
> experimented with in this Community Group. We have a good group of
> domain experts and browser folks in this CG, so this is a good place to vet
> your idea, attract contributions from the wider community.
> 
> For example, extensions to the Presentation API that are deemed out of
> scope for the Working Group might be good candidates to be experimented
> in this CG.
> 
> If new proposal for deliverables are identified and there are people
> interested in driving them forward, we'll update the CG Charter as needed
> per [3].
> 
> Thanks,
> 
> -Anssi (CG chair)
> 
> [1] https://www.w3.org/community/webscreens/
> [2] http://www.w3.org/2014/secondscreen/
> [3] https://github.com/webscreens/presentation-api/wiki/Second-Screen-
> Community-Group-Charter#amendments-to-this-charter
Received on Thursday, 8 October 2015 19:56:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:23:16 UTC