W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2015

Re: [presentation-api] possible charter for second screen cg - 2 UA communication

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Nov 2015 21:57:56 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-155922403-1447279075-sysbot+gh@w3.org>
@wcarr Thanks for putting an initial draft together for feedback.

I am quite concerned that the proposed scope of the carter omits the 
1-UA case. This was specifically mentioned as important by me in the 
Sapporo F2F.   In fact this could be an easier use case to achieve 
interoperability because there is a complete, self contained, open 
source implementation available (WebRTC).

Imagine having a Raspberry Pi hooked up to a TV.  Many HTML5 documents
 will perform poorly given its memory and CPU constraints and lack of 
GPU.  But it is perfectly suitable for rendering a WebRTC stream at 
720p or better.

I think the wording of the example architecture could be improved.  
For example it would be better to list specific requirements for each 
of the components and list example technologies that could be listed 
to implement them.

The charter should make clearer what specifications may be produced.  
In IETF style, the specifications will more likely follow the 
architectural layering and not the use case.  For example there could 
be a specification for LAN discovery and control via TCP/IP, discovery
 and control via BLE/GATT, and a signaling protocol layered on top of 
either - that would be three specs.

There is no way to send control messages via DIAL so I don't think 
it's worth mentioning as an example technology.  It simply does not 
meet the baseline requirements for Presentation API. 

I don't want to overpromise on BLE.  It can be used as a discovery 
mechanism but to implement control would likely require going through 
the Bluetooth SIG to register a new GATT service type.  The security 
architecture is a bit of a mystery as well.  I think it is a promising
 technology but I don't want to commit to it in our scope until due 
diligence has been done.

GitHub Notif of comment by mfoltzgoogle
Received on Wednesday, 11 November 2015 21:57:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:59 UTC