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

Introduce an appendix cataloging old terminology #898

Merged
merged 5 commits into from
Aug 15, 2024
Merged

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Jul 11, 2024

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Jul 11, 2024
@frivoal frivoal marked this pull request as ready for review July 11, 2024 03:08
@frivoal frivoal added this to the Process 2024 milestone Jul 11, 2024
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
frivoal and others added 2 commits July 24, 2024 05:05
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
@frivoal
Copy link
Collaborator Author

frivoal commented Jul 24, 2024

Copy link
Member

@TallTed TallTed left a 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.

index.bs Outdated Show resolved Hide resolved
index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
index.bs Show resolved Hide resolved
Co-authored-by: Ted Thibodeau Jr <[email protected]>
@frivoal
Copy link
Collaborator Author

frivoal commented Jul 24, 2024

@TallTed

Consistently precedes the <a ...> with the in.

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 <a> tag, which links to the specific anchor, as I am linking to something "in the section". When the term has no link, and the only think I can link to is the section, I have put "in" outside of the <a> tag, as I am linking to the section.

@TallTed
Copy link
Member

TallTed commented Jul 24, 2024

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.

@frivoal
Copy link
Collaborator Author

frivoal commented Jul 24, 2024

Any alternative suggestion, other than uniformizing as you've proposed earlier?

@fantasai
Copy link
Collaborator

Consistently include "in"? Hitting the top of the section or a dfn inside, either way it's in the section.

@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Introduce an appendix cataloging old terminology, and agreed to the following:

  • RESOLVED: Merge PR 898 Introduce glossary of old terms
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

@css-meeting-bot css-meeting-bot removed the Agenda+ Marks issues that are ready for discussion on the call label Aug 14, 2024
@frivoal frivoal merged commit 7fd5a10 into w3c:main Aug 15, 2024
2 checks passed
@frivoal frivoal added the Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion label Aug 15, 2024
@frivoal frivoal deleted the old-terms branch September 12, 2024 04:49
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 Type: Editorial improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants