-
Notifications
You must be signed in to change notification settings - Fork 49
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
Generalize principle about avoiding abbreviations? #276
Comments
This came up here: w3ctag/design-reviews#547 (comment) Edit: We suggested |
Counterexamples that are fine to abbreviate are probably ones that are canonically used in abbreviated form. (like names of common standards, e.g. DOM) Not sure where rAF fits in though. |
@cynthia I was primarily referring to abbreviations that are not acronyms or initialisms. Those are a whole different topic. |
Other considerations:
|
Ah, this reminded me to file #285 that I've had in my back burner for a while. |
Understood. (Abbreviation and acronym are the same word in my native tongue, in my defense.) |
There is currently no rule against abbreviations in the "naming" section, but there is this sentence in the 3.4. Naming of CSS properties and values section (should this be moved to the naming section?):
This seems more broadly applicable, but I'm not sure of the extent. For example, HTML: In the past, we'd heavily abbreviate names of HTML elements (e.g.
<img>
,<ul>
,<h1>
etc), whereas recently this is less common (e.g.<video>
,<source>
(not<src>
),<header>
,<datalist>
etc).In JS, there are several abbreviations, some common, some less so, e.g.
Id
,async
,Intl
,BigInt
,RegExp
,UInt
to name a few.It might be good to figure out what the rule should be here, i.e. can we define in which cases abbreviations are a good idea and in which cases they are not? It seems this depends on:
The text was updated successfully, but these errors were encountered: