- From: Stephen Zilles <szilles@adobe.com>
- Date: Sun, 19 Apr 2015 16:44:57 +0000
- To: "public-w3process@w3.org" <public-w3process@w3.org>
- CC: "ab@w3.org" <ab@w3.org>
- Message-ID: <BN1PR0201MB0802707AF74D6B952ECA740AAEE10@BN1PR0201MB0802.namprd02.prod.outlook.>
In my previous message, I neglected to add the two edits that resolve Issue-152[0] which is concerned with Edited Recommendations with only Editorial Changes. These edits are: [0] a. In Section 7.7.2, the second paragraph after the Issue Replace "Editorial changes to a Recommendation require no technical review of the proposed changes. A Working Group may request publication of a Proposed Recommendation or W3C may publish a Proposed Recommendation to make this class of change without passing through earlier maturity levels. Such publications may be called a Proposed Edited Recommendation." With "Editorial changes to a Recommendation require no technical review of the proposed changes. A Working Group, provided there are no "No" votes in the resolution to publish, may request publication of an Edited Recommendation to make this class of change without passing through earlier maturity levels. If there are any "No" votes, the Working group must follow the process, below, for Substantive Changes" b. In Section 7.2.5, item 2. "Corrections that do not affect conformance" Replace "Editorial changes or clarifications that do not change the technical content of the specification." With "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 are 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 belong to this class." The Process Document Task Force agreed to make the following changes to the March 3, 2015 draft of Process 2015 [1] prior to submission for AC Review. [1] https://dvcs.w3.org/hg/AB/raw-file/68f2be460152/cover.html 1. In the introduction, in the sentence "When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an Advisory Committee mailing list https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#ACCommunication ), the Director announces the development of a proposal for one or more new https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#ActivityDevelopment> or Interest Group or Working Group charter https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#WGCharterDevelopment, depending on the breadth of the topic of interest." Remove the link on "new" (which is to Activities) and the following "or" and make "charter" plural, reading, "announces the development of a proposal for one or more Interest Group or Working Group charters" [with a link on "Interest Group and Working Group charters" to https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#WGCharterDevelopment]. 2. In Section 2.2 The Team. "assessing consensus https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#def-Consensus within W3C for architectural choices, publication of technical reports<https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#Reports>, and new activities;" Change "activities" to "Groups". 3. In Section 2.5.2, change "not required" to "NOT REQUIRED" . 4. In Section 6.2.1 change "may" to "MAY" 5. In Section 6.2.2 "Advisory Committee representatives may express their general support on the Advisory Committee discussion list ." Change "express their general support" to "provide feedback" 6. In 6.2.6, bullet 5, replace the sentence that begins with " * Any dependencies by groups within or outside of W3C on the deliverables of this group." With " * Any dependencies by groups within or outside of W3C on the deliverables of this group. Such dependencies include interactions with W3C Horizontal Groups." [with a link on "W3C Horizontal Groups" to http://www.w3.org/Guide/Charter.html#horizontal-review ] followed by the remainder of the bullet point. 7. In 7.2.3.1, paragraph 1 replace "Before approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document, who has provided comments, the record of requests to and responses from reviewers, especially groups identified as dependencies in the charter or identified as liaisons [PUB29], and seek evidence of clear communication to the general public about appropriate times and which content to review and whether such reviews actually occurred." With "Before approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document, who has provided comments, the record of requests to and responses from reviewers, especially W3C Horizontal Groups and groups identified as dependencies in the charter or identified as liaisons [PUB29], and seek evidence of clear communication to the general public about appropriate times and which content to review and whether such reviews actually occurred." [with a link on "W3C Horizontal Groups" to http://www.w3.org/Guide/Charter.html#horizontal-review ]. This change adds, "W3C Horizontal Groups and" after "especially" in the Process 2014 text. Steve Zilles Chair, Process Document Task Force
Received on Sunday, 19 April 2015 16:45:31 UTC