Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retitle STATUS Sections to Avoid Double Definitions #336

Closed
fantasai opened this issue Oct 23, 2019 · 3 comments
Closed

Retitle STATUS Sections to Avoid Double Definitions #336

fantasai opened this issue Oct 23, 2019 · 3 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) Type: Editorial improvements
Milestone

Comments

@fantasai
Copy link
Collaborator

The current Chapter 6 of the Process is a bit hard to follow, partly because it seems to define each status in two places: under 6.1.2 where it actually defines what each status means, and as direct subheadings of Chapter 6, e.g. 6.4 Candidate Recommendation which mostly just explains how to get from WD to CR.

Proposal is to retitle the sections about how to get from A to B as "How to get from A to B" or somesuch, leaving the actual definitions of A and B in 6.1.2. (There's a few bits of definition mixed in with the process instructions, but we should just pull them out into 6.1.2.) This leaves us with a clean and complete definition of each phase in one place, and lets the sections that are largely about transition processes be purely about transition processes (and be titled clearly as such).

@fantasai
Copy link
Collaborator Author

fantasai commented Oct 23, 2019

Basically, if the REC track were a flow chart, we define the boxes in 6.1.2, and we define the arrows as a series of sections starting with 6.3. We don't mix bits of box definitions in with the arrow definitions or vice versa. And we title the arrow sections as arrows to/from particular boxes, not as the name of their "from" boxes.

@dwsinger
Copy link
Contributor

Agreed. Most of the sections of 6.x after 6.2 start with a verb ("modifying" "obsoleting") and one has the magic word "publishing". I suggest we add "Publishing" in the titles of 6.3, 6.4, 6.5, replace "W3C" with "Publishing" in 6.6

6.3 Working Draft
6.4 Candidate Recommendation
6.5 Proposed Recommendation
6.6 W3C Recommendation
6.7 Modifying a W3C Recommendation
6.8 Publishing a Working Group or Interest Group Note
6.9 Declaring a W3C Recommendation Rescinded, Obsolete or Superseded

@dwsinger dwsinger added Agenda+ Marks issues that are ready for discussion on the call Type: Editorial improvements labels Oct 23, 2019
@frivoal
Copy link
Collaborator

frivoal commented Nov 8, 2019

Done for the everblue/teal branch with 5849d59...98d009b

@frivoal frivoal added the Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion label Jan 9, 2020
@frivoal frivoal closed this as completed Jan 9, 2020
@frivoal frivoal added this to the Process 2020 milestone Jan 9, 2020
@frivoal frivoal removed the Agenda+ Marks issues that are ready for discussion on the call label Jan 9, 2020
@frivoal frivoal added the DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) label Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) Type: Editorial improvements
Projects
None yet
Development

No branches or pull requests

3 participants