-
Notifications
You must be signed in to change notification settings - Fork 130
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
Introduce an appendix cataloging old terminology #898
Conversation
Co-authored-by: Ted Thibodeau Jr <[email protected]>
* merge the two lists * use alphabetical order * use more consistent phrasing * use as specific a link as possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consistently precedes the <a ...>
with the in
.
Co-authored-by: Ted Thibodeau Jr <[email protected]>
There was actually a logic to the way I have done it: when it is possible to link to the term itself, I have included "in" inside the |
I understand your logic, now you've explained it. As they will lack that explanation, however, I think new readers will find the inconsistency meaningless at best and confusing at worst. I'll live with whatever the CG thinks. |
Any alternative suggestion, other than uniformizing as you've proposed earlier? |
Consistently include "in"? Hitting the top of the section or a dfn inside, either way it's in the section. |
The Revising W3C Process CG just discussed
The full IRC log of that discussion<fantasai> florian: This is the appendix of retired terms<fantasai> ... including "Proposed Recommendation" <fantasai> ... addressed all of TallTed's comments <fantasai> ... one he didn't confirm yet was fixing the consistency of whether "in" is part of the hyperlinks <fantasai> cwilso: In general I think it's fine, we can merge <fantasai> ... only thought is, would it be useful to say what happened to the terms? Like why they're not relevant. <fantasai> florian: For ones that were renamed, I mentioned <fantasai> ... those retired, it wasn't the term retired, but the thing it refers to <fantasai> ... could put a description here but that's redundant with the change sections of the processes that retired them <fantasai> ... info is out there, didn't link directly to it though <fantasai> florian recaps discussion now that TallTed is here <fantasai> florian: if someone wants to link to old changelogs, can do in a follow up commit <fantasai> ... don't want to reproduce the rationale in-line -- might get it wrong, and it's too much text for such an appendix <fantasai> RESOLVED: Merge PR 898 Introduce glossary of old terms |
See https://github.com/w3c/process/pull/868/files?diff=unified&w=1#r1654549592 for context.
Preview | Diff