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

chore: replace informative with non-normative for consistency #1015

Merged
merged 4 commits into from
Apr 6, 2025

Conversation

Bashamega
Copy link
Contributor

@Bashamega Bashamega commented Mar 28, 2025

fixes #914


Preview | Diff

@Bashamega
Copy link
Contributor Author

Done @frivoal :)

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Mar 28, 2025
@frivoal
Copy link
Collaborator

frivoal commented Mar 28, 2025

Thank you @Bashamega. Help improving the quality and consistency of the text is always very much appreciated!

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.

s/an non-normative/a non-normative/
:-)

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
@nigelmegitt
Copy link
Contributor

Thanks for addressing this @Bashamega - please could you also address the terminology in the Document Conventions section, and the example within it?

I also just noticed that the non-normative references, which are generated by tooling, are in a section called "Informative references" - I don't know if that can be changed, but in #914 when we discussed the preference for non-normative vs informative, that would have been a useful data point!

The deliberate cases where "informative" were left are now looking quite confusing to me. Perhaps we should replace them with "informational" or something else that makes it clear that it is not a synonym for "non-normative"?

@frivoal
Copy link
Collaborator

frivoal commented Apr 6, 2025

@nigelmegitt The other parts are not coming from the source code, but from bikeshed (speced/bikeshed#3077). I'll follow up to get that addressed there, but this PR is a net improvement.

As for the remaining instances of informative in the text, I think they're actually quite natural and better than alternative rephrasing (like "informational"). Unless you're specifically looking for them as we are here, I think it's unlikely anybody would notice anything unusual about them.

@frivoal frivoal merged commit e16de99 into w3c:main Apr 6, 2025
2 checks passed
@frivoal frivoal added Type: Editorial improvements Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Marks issues that are ready for discussion on the call labels Apr 6, 2025
@frivoal frivoal added this to the Process 2024/2025 milestone Apr 6, 2025
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.

Be consistent with terms "non-normative" and "informative"
6 participants