[css2] Naming of revision of CSS 2.1

[gsnedders]

As far as I can tell, looking through WG minutes, we never decided what to call the revision of CSS 2.1 incorporating errata. I think we have two options:

• CSS 2.1 2nd Edition
• CSS 2.2

I'm in favour of CSS 2.1 2nd Edition because with the exception of scientific notation for numbers, we haven't added/removed any features, it's a simple update to incorporate errata, and as such in my view it doesn't constitute a new subversion of CSS 2.

[SelenIT]

Doesn't the third formatting context (Table) count as a feature?

[frivoal]

Which one are you talking about: CSS2.1 + with all the work in progress errata, or the one with the limited subset or errata that are ready for REC republication?

I think the later does not need a new name at all. It's just CSS2.1, and if you want to be very specific, you can still say CSS2.1, 07 June 2011 Recommendation, or CSS2.1 29 February 2019.

For the former, it probably should have a name, but not a new version number, since it isn't meant to be a new document that ever gets published as a replacement for the 2.1 REC, just a staging area for changes. So I'd call it something along these lines: "CSS2.1, errata staging draft"

[SelenIT]

I'd prefer following the pattern consistent with the HTML spec development:

• CSS2.1 2nd Edition (like HTML5.1 2nd Edition) as a republished REC, with the limited subset of errata incorporated;
• its own Editor's draft (like https://rawgit.com/w3c/html/html5.1-2/single-page.html) as its errata staging draft, without the separate published verion;
• CSS2.2 (like HTML5.2), with all CSS2.1 errata incorporated and all sections that have been updated with newer CSS modules replaced with links to those modules, as a future CSS2.x release that will eventually replace the CSS2.1 as the "Latest CSS level 2";
• Editors draft of "the latest CSS level 2" pointing to the latest state of CSS2.x development (like https://w3c.github.io/html/).

Just changing the publication date, without updating the spec name, doesn't seem enough to me because people might conclude that it was just a formal editorial update (like adding the red warning box in 2016). However, the errata contain some changes in the specified behavior (e.g. rules of margin collapsing) and terminology (e.g. the term "Table Formatting Context" occurs only in the errata), which can lead to confusion.

[tantek]

I can see reasons for using either "CSS 2.1 nth edition" or "CSS 2.2 (nth edition)" moving forward. In either case we should use "++nth edition" for subsequent updates rather than incrementing the decimal. Here is what I could come up with and or saw or heard mentioned by others:

Arguments for CSS 2.1 nth edition moving forward:

• no new features, so no need to increment the decimal
• past decision(s) that CSS 2.1 would be the last version of CSS2.
• avoid version number inflation

Arguments for CSS 2.2 nth edition moving forward:

• CSS 2.1 has been a stable (unchanging) document for many years, "2nd edition" does not accurately reflect the extent of likely editorial and substantive edits necessary to incorporate years of accumulated errata and issues
• "CSS 2.2" explicitly sends a signal to browser implementers and detail-oriented web developers that it has (will have) major bug fixes since CSS 2.1 that everyone else has read and referenced (in books etc.)
• Regular updates is a new mode. Since the proposed CSS 2.x editing & publishing workflow (see CSS2 maintenance proposal #2553) will be publishing regular updates with changes, it makes sense to provide a new decimal version number to signal this change in expected maintenance as well
• A CSS 2.2 WD has been published, and will forever exist. It would now look weird (possibly be confusing) to have the "latest" CSS 2.x be 2.1, a perceived step backwards from the 2.2 WD
• A single decimal increment over the course of 10+ years is reasonable and provides no danger immediate or subsequent of version number inflation

Based on these reasons, I have some preference for now (continuing) moving forward with CSS 2.2 on the condition that our proposed seasonal/regular iterations use "nth edition" rather than incrementing the decimal.

I also agree that "Just changing the publication date, without updating the spec name, doesn't seem enough to me".

I would be open to incrementing the decimal in the distant future if we make major changes such as replacing whole chapters with normative references to CSS 3 modules, or perhaps obsoleting a whole chapter in deference to one or more CSS module(s) (e.g. perhaps colors.html with css-color-3 and css-backgrounds-3).

PROPOSED: Use CSS 2.2 for the next REC track revision of CSS 2.1, and then append "2nd edition", "3rd edition" etc. for subsequent Edited Recommendations.

(Originally published at: http://tantek.com/2018/102/t5/)

[css-meeting-bot]

The Working Group just discussed Naming of revision of CSS 2.1, and agreed to the following resolutions:

• RESOLVED: Use the naming scheme proposed at bottom of https://github.com/w3c/csswg-drafts/issues/2008

The full IRC log of that discussion

<dael_> Topic: Naming of revision of CSS 2.1
<dael_> github: https://github.com//issues/2008
<dael_> tantek: Now that we have an agreed workflow for 2.1, gsnedders opened this last NOv as to what do we call it. 2.2 or 2.1 nth edition. There has been some back and forth. I can argue for either. Wrote a summary at the bottom.
<dael_> tantek: Based on that my proposal is go with CSS 2.2 nth edition.
<dael_> tantek: Major reason is 2.1 has been stable and unchanging for so many years that adding editions would not indicate we're applying these changes. We've also already published 2.2 WD so it'll always be there.
<dael_> fantasai: We can make the permalink repoint. We've done that before.
<dael_> florian: Not sure we have. I think we have both links serve same content.
<dael_> tantek: Regardless, we published and it's out there.
<dael_> tantek: So 2.2 nth edition. 2.2 2nd edition 2.2 3rd edition etc.
<dael_> florian: POint is URL stays the same.
<dael_> fantasai: Should always be CSS 2.
<dael_> fantasai: I think it's important to make sure it replaces this
<fantasai> Need to replace https://www.w3.org/TR/CSS21/
<dael_> florian: Unless you put in a dated URL any should link you to the latest 2.2
<dbaron> you mean like https://www.w3.org/TR/REC-CSS2/ gives me the 1998 REC... ?
<dael_> fantasai: A lot of links point into that. Whatever we publish should replace that.
<dael_> tantek: Agree.
<dbaron> (I thought we fixed that at some point...)
<dael_> fantasai: I think having CSS2.1 point to CSS 2.2 is weird but if you want to.
<dael_> gsnedders: And we need to make sure that whoever approves is okay that /css21 points to /css22.
<dael_> dbaron: Sounds like the sort of thig we can convince plh to do.
<dael_> astearns: Do we change editions for only substantive changes?
<dael_> fantasai: Depends on process.
<dael_> tantek: Process doesn't say.
<dael_> gsnedders: I think every new ER has a new number.
<dael_> astearns: Okay.
<dael_> tantek: That's what I rpopose
<dael_> florian: Not a new short name
<dael_> fantasai: Short name stays CSS2.2
<fantasai> s/CSS2.2/CSS2/
<dael_> astearns: Obj to the naming scheme proposed at bottom of https://github.com//issues/2008 ?
<dael_> astearns: [reads]
<dael_> gsnedders: how many people favored 22 over 21 that you spoke to.
<dael_> tantek: That was gathering, a lot of people weren't very strong.
<tantek> PROPOSED: Use CSS 2.2 for the next REC track revision of CSS 2.1, and then append "2nd edition", "3rd edition" etc. for subsequent Edited Recommendations.
<dael_> florian: I'm okay with either.
<tantek> (copy pasted from bottom of 2008)
<dael_> astearns: Shall we resolve?
<dael_> RESOLVED: Use the naming scheme proposed at bottom of https://github.com//issues/2008

[gsnedders]

CSS 2.1 has lots of statements like:

But, in CSS 2.1, it is undefined whether the decoration propagates into block-level tables.

What do we want to change this to? Given the plan is presumably to obsolete/supersede 2.1 (and we should probably make 2.0 obsolete), do we just want to say "in CSS 2"?

[gsnedders]

@tantek I'm leaving it down to you to make the required edits and change the status (in the Makefile) back to ED to bump us to 2.2, though please do this soon so we can start relanding changes. (Unless you're happy with us temporarily being an ED of 2.1?)