- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Jan 2016 16:22:28 +0000
- To: public-secondscreen@w3.org
@anssiko I will provide text for the Status of This Document section. With the risk of delaying the publication a bit... Re-reading the spec and the list of open issues, if we want to use the publication to encourage a "wide review" of the spec, wouldn't it make sense to make a small push to fix the "known bugs", by which I mean the parts where we know that the spec is wrong or incomplete and that should only require a Pull Request? I'm thinking about the following issues in particular: #165 conflict description for uniquely identifying a presentation session #193 Define a "set of presentations" for the receiving context? #211 binaryType attribute's default value and get/set behaviour needs to be specified #229 Need algorithm for establishing a presentation connection when the previous connection(s) were closed #245 "Known connection" in reconnect() may be linked to another browsing context That seems doable in a reasonable amount of time, and that would only leave open issues about informative guidelines, possible enhancements, meta-issues and a couple of more long-lasting discussions. I'm willing to take a stab at most of the issues listed above next week, at least. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/244#issuecomment-176843851 using your GitHub account
Received on Friday, 29 January 2016 16:22:32 UTC