- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sun, 09 Jan 2022 13:00:26 +0000
- To: public-css-archive@w3.org
Compare - [Updating an existing Recommendation with editorial changes](https://www.w3.org/Guide/transitions?profile=REC&rec=editorial) - [Incorporating candidate corrections (substantive changes) into an existing Recommendation](https://www.w3.org/Guide/transitions?profile=REC&rec=substantive) so the discussion boils down to "are all of [these changes](https://www.w3.org/TR/css-color-3/#changes) editorial, or is any one of them substantive? 1. Candidate Correction 1: **Sample HSL values & conversion code.** The samples are explicitly non-normative. The code does not claim to be normative, but does not explicitly say it is informative either. 2. Candidate Correction 2: **Clarified case-insensitive.** Since all the existing color names are ASCII-only, the clarification that "case insensitive means ASCII case insensitive" has no substantive impact. 3. Candidate Correction 3: **Removed "Media" from property definition tables** same as all recent specs. I don't think removing `Media: visual` has any substantive impact on the `color` property. 4. Candidate Correction 4: **Replaced "Call for implementation of dropped features"** That section, which contained no normative statements but called for implementations of dropped features like `@color-profile`, has been replaced by an (explicitly non-normative) forward pointer to the higher-level specs where those features are now defined. So, editorial. My proposal to the group is therefore that all four of these changes are editorial and so we can follow the "Updating a Rec with entirely editorial changes" route. If the group finds one or more of these to be substantive, then we need to follow the more lengthy (Last Call for the AC, etc) route for the substantive one(s). The remaining editorial ones can be simply folded in at the same time. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6910#issuecomment-1008293420 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 9 January 2022 13:00:27 UTC