Follow up on normativity warnings about glossary

[aphillips]

Note to PLH sent on 2024-11-22:

---

Hi PLH,

I am reminded today of a TPAC conversation we had about the I18N Glossary [1], having noticed the problem in our review of Input Events [2].

We encourage the use of the glossary for linking common terminology in specs vs. having to clone the definition locally (with all of the maintenance headaches that ensue). The glossary is published as a NOTE, so is not normative. Uses of our terminology do not generally affect normativity, but linking the terms improves understanding. When the term is used in a normative way, Infra is usually the host to the term and we work with WHATWG et al to keep from having any conflicts.

However, this means that references to our glossary produce respec warnings about “non-normative reference in a normative block”. You’ll recall that in our conversation we agreed that the I18N glossary should be an exception to this. Before I approach the Specref et al folks about this, I wanted to remind you and see if you had any comments or have developed any concerns.

Thanks,

Addison

[1] https://www.w3.org/TR/i18n-glossary/
[a] https://github.com/w3c/i18n-glossary
[2] https://w3c.github.io/input-events/#interface-InputEvent-Attributes (notice insertTranspose)

[aphillips]

w3c/guide#269

[aphillips]

Emailed PLH today privately (cc: @xfq and @r12a)

[ghurlbot]

Closed by @aphillips via IRC channel #i18n on irc.w3.org