- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Aug 2016 14:35:41 +0000
- To: public-annotation@w3.org
@tantek, just to put the admin issue at rest: > 6.4.1 Revising a Candidate Recommendation > > If there are any substantive changes made to a Candidate Recommendation other than to remove features explicitly identified as "at risk", the Working Group must obtain the Director's approval to publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a new Exclusion Opportunity per section 4 of the W3C Patent Policy [PUB33]. Note that approval is expected to be fairly simple compared to getting approval for a transition from Working Draft to Candidate Recommendation. > In addition the Working Group: > > • must show that the revised specification meets all Working Group requirements, or explain why the requirements have changed or been deferred, > • must specify the deadline for further comments, which must be at least four weeks after publication, and should be longer for complex documents, > • must document the changes since the previous Candidate Recommendation, > • must show that the proposed changes have received wide review, and > • 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. > The Director _MUST_ announce the publication of a revised Candidate Recommendation to other W3C groups and the Public. See https://www.w3.org/2015/Process-20150901/#revised-cr As the text does say that the Director's approval is probably quicker than for the first round, but we cannot just re-issue a document without further ado. We need to get approval, republish, and all that jazz. (I have also checked the [2016 version of the process](https://dvcs.w3.org/hg/AB/raw-file/cfef536bff0d/cover.html#revised-cr) and, as far as I can see, there is no difference.) Anyway. We should not get bogged down in admin issues, but we should also avoid overcomplicating our lives. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/335#issuecomment-238085951 using your GitHub account
Received on Sunday, 7 August 2016 14:37:48 UTC