{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/presentation-api/issues/406","repository_url":"https://api.github.com/repos/w3c/presentation-api","labels_url":"https://api.github.com/repos/w3c/presentation-api/issues/406/labels{/name}","comments_url":"https://api.github.com/repos/w3c/presentation-api/issues/406/comments","events_url":"https://api.github.com/repos/w3c/presentation-api/issues/406/events","html_url":"https://github.com/w3c/presentation-api/issues/406","id":201211802,"number":406,"title":"[meta] Publish a revised Candidate Recommendation","user":{"login":"anssiko","id":765510,"avatar_url":"https://avatars.githubusercontent.com/u/765510?v=3","gravatar_id":"","url":"https://api.github.com/users/anssiko","html_url":"https://github.com/anssiko","followers_url":"https://api.github.com/users/anssiko/followers","following_url":"https://api.github.com/users/anssiko/following{/other_user}","gists_url":"https://api.github.com/users/anssiko/gists{/gist_id}","starred_url":"https://api.github.com/users/anssiko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anssiko/subscriptions","organizations_url":"https://api.github.com/users/anssiko/orgs","repos_url":"https://api.github.com/users/anssiko/repos","events_url":"https://api.github.com/users/anssiko/events{/privacy}","received_events_url":"https://api.github.com/users/anssiko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-01-17T09:05:30Z","updated_at":"2017-01-25T09:48:29Z","closed_at":null,"body":"[All - please let us know if you have any comments or concerns with this publication plan. Silence is considered consent.]\r\n\r\nThere has been [substantive changes][1] to the Presentation API since the latest [Candidate Recommendation 14 July 2016][2] thanks to extensive implementation feedback and findings from the conformance testing of the API. See also the [visual HTML diff][3] between the CR and the latest [Editor's Draft][4]. Given that, we should publish a revised Candidate Recommendation.\r\n\r\nPer the [process for revising a CR][5], the group needs to address the following requirements to make that happen:\r\n\r\n- [x] must show that the revised specification meets all Working Group requirements, or explain why the requirements have changed or been deferred,\r\n- [ ] must specify the deadline for further comments, which must be at least four weeks after publication, and should be longer for complex documents,\r\n- [ ] must document the changes since the previous Candidate Recommendation,\r\n- [ ] must show that the proposed changes have received wide review, and\r\n- [ ] may identify features in the document as \"at risk\". These features may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.\r\n\r\nTo tick the boxes, I suggest we:\r\n\r\n* use the deadline of four weeks for further comments,\r\n* document high-level changes since the first CR in the Status of This Document section, and in addition, link to the [GitHub compare][1] (or the HTML diff) for the detailed changes (@mfoltzgoogle could you help compile the high-level list?), \r\n* regarding the wide review of the changes, @tidoust let us know your recommendation how to handle the wide review of the delta,\r\n* document \"at risk\" features in the SoTD section as well -- implementers @mfoltzgoogle @schien et al.: please let us know if there are features in the spec you are considering not to implement.\r\n\r\nFinally, after we've ticked the above boxes, @tidoust will help us acquire the approval from the Director to publish a revision, and I expect will help prepare a publication-ready updated CR snapshot:\r\n\r\n- [ ] must obtain the Director's approval to publish a revision of a Candidate Recommendation\r\n\r\n[1]: https://github.com/w3c/presentation-api/compare/gh-pages@%7B2016-07-14%7D...gh-pages\r\n[2]: https://www.w3.org/TR/2016/CR-presentation-api-20160714/\r\n[3]: http://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2016%2FCR-presentation-api-20160714%2F&doc2=https%3A%2F%2Flabs.w3.org%2Fspec-generator%2F%3Ftype%3Drespec%26url%3Dhttps%253A%252F%252Frawgit.com%252Fw3c%252Fpresentation-api%252Fgh-pages%252Findex.html%253FspecStatus%253DED%253BshortName%253Dpresentation-api\r\n[4]: https://w3c.github.io/presentation-api/\r\n[5]: https://www.w3.org/2015/Process-20150901/#revised-cr"},"comment":{"url":"https://api.github.com/repos/w3c/presentation-api/issues/comments/275063796","html_url":"https://github.com/w3c/presentation-api/issues/406#issuecomment-275063796","issue_url":"https://api.github.com/repos/w3c/presentation-api/issues/406","id":275063796,"user":{"login":"anssiko","id":765510,"avatar_url":"https://avatars.githubusercontent.com/u/765510?v=3","gravatar_id":"","url":"https://api.github.com/users/anssiko","html_url":"https://github.com/anssiko","followers_url":"https://api.github.com/users/anssiko/followers","following_url":"https://api.github.com/users/anssiko/following{/other_user}","gists_url":"https://api.github.com/users/anssiko/gists{/gist_id}","starred_url":"https://api.github.com/users/anssiko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anssiko/subscriptions","organizations_url":"https://api.github.com/users/anssiko/orgs","repos_url":"https://api.github.com/users/anssiko/repos","events_url":"https://api.github.com/users/anssiko/events{/privacy}","received_events_url":"https://api.github.com/users/anssiko/received_events","type":"User","site_admin":false},"created_at":"2017-01-25T09:48:29Z","updated_at":"2017-01-25T09:48:29Z","body":"See https://github.com/w3c/presentation-api/issues/380#issuecomment-275063423 for my summary of the WebAppSec WG's position on [SecureContext] and suggested next steps."}}
{"actor":{"display_login":"anssiko"}}