- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Nov 2015 18:10:55 +0000
- To: public-secondscreen@w3.org
I think the main reasons for starting this work are: 1. to define a base set of protocols that Presentation API implementers can refer to to implement the spec; 2. to improve interoperability between implementations, i.e. the possibility to associate a presentation controller with a presentation receiver even if they have not been implemented by the same user agent. While I would love to see all possibilities covered, I would initially restrict the scope to developing the necessary glue around technologies that participants can agree on and plan to implement right away. For instance, mDNS appears in all proposals/implementation plans, so it seems like a good starting point for discovery. BLE could perhaps be addressed later on. The charter should leave the door open for the CG to write requirements for additional technologies in any case (the proposed draft charter allows that), even though related technical specifications remain out of scope. It should be relatively easy to update the CG charter to extend the scope once participants agree that some other technology needs to be covered. Well, at least it should be easier than doing the same thing in a Working Group. -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/220#issuecomment-156187294
Received on Thursday, 12 November 2015 18:10:57 UTC