- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Apr 2016 13:38:09 +0000
- To: public-secondscreen@w3.org
@anssiko, I agree that #202 (Presentations without communication channel) can be considered a new feature and defered to v2. I updated issue labels accordingly. Although not explicit in the [CR requirements](https://www.w3.org/2015/Process-20150901/#candidate-rec), publication as CR normally implies that known technical issues have been addressed and more generically that the group has solved all issues that could lead to normative changes in the spec. We also need to demonstrate that the specification has undergone wide review. As such, I would add at least the following issues to the list of issues to be solved before CR: - #162 Evaluate Presentation API against the Media Accessibility User Requirements spec - #163 PresentationSession should have stream interfaces! - #218 Possibility for a character to be interpreted differently depending on locale - #241 bufferedAmount property on PresentationConnection - #253 Have the receiving browsing context generate the presentation identifier? - #254 When is the first presentation connection created in the receiving browsing context? - #269 Only allow one PresentationAvailability per PresentationRequest - #273 PresentationConnectionClosedEventInit.message needs to have a default value Some of these issues may need to be discussed at the F2F, but most of them simply need some sort of "PR" (Pull Request or Proposed Resolution). Essentially, I'd like to propose the same game as in January: let's kill some issues so that the spec may be published as CR shortly after the F2F! -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/276#issuecomment-206377135 using your GitHub account
Received on Wednesday, 6 April 2016 13:38:11 UTC