- From: Philippe Le Hégaret <plh@w3.org>
- Date: Thu, 27 Oct 2016 08:27:22 -0400
- To: "public-hme-editors@w3.org" <public-hme-editors@w3.org>
Because the current plan is not to have a Working Group beyond the current one, I wanted to list our options to maintain the Recommendations in the meantime. I'm using Process 2016 below since I expect it to be effective in the upcoming 3 months. at least for now, per [1], W3C won't be allowed to make changes of type 3: [[ 3. Corrections that do not add new features These changes may affect conformance to the specification. A change that affects conformance is one that: makes conforming data, processors, or other conforming agents become non-conforming according to the new version, or makes non-conforming data, processors, or other agents become conforming, or clears up an ambiguity or under-specified part of the specification in such a way that data, a processor, or an agent whose conformance was once unclear becomes clearly either conforming or non-conforming. ]] https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#editorial-change Without a Working Group we can however do changes of type 1 and 2: [[ 1. No changes to text content These changes include fixing broken links, style sheets or invalid markup. 2. Corrections that do not affect conformance Changes that reasonable implementers would not interpret as changing architectural or interoperability requirements or their implementation. Changes which resolve ambiguities in the specification are considered to change (by clarification) the implementation requirements and do not fall into this class. Examples of changes in this class include correcting non-normative code examples where the code clearly conflicts with normative requirements, clarifying informative use cases or other non-normative text, fixing typos or grammatical errors where the change does not change implementation requirements. If there is any doubt or dissent as to whether requirements are changed, such changes do not fall into this class. ]] https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#editorial-change We'll need to update the errata page first then, after a few months, it could make sense to fold the errata list into an Edited Recommendation. If we want to publish an errata and/or an "Edited Recommendation", I'd recommend that the editors simply ping me, cc the public mailing list (and/or open a GitHub issue and ping me there and by email). Also note that we allow the following types of changes *in-place* (ie without publishing a new REC with a new date): [[ a. Fixes to broken markup (e.g., invalid markup) b. Fixed to broken links (i.e., URIs) c. Fixes to broken style sheets d. Some visible status updates, such as adding big indicator to point to newer versions ]] https://www.w3.org/2003/01/republishing/ If we do want to make changes of type 3, we'll need to reconsider closing the Group and propose a narrowed scoped charter that only allow changes of type 3. If you have questions, don't hesitate to ask. Philippe [1] https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#revised-rec
Received on Thursday, 27 October 2016 12:27:30 UTC