-
Notifications
You must be signed in to change notification settings - Fork 16
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
Rename "ancillary" to "supporting" and "non-ancillary" to "essential." #438
base: main
Are you sure you want to change the base?
Conversation
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.
I have a slight concern about changing "ancilliary" to "supporting", as "ancilliary" is somewhat neutral whereas "supporting" may be interpreted as describing these uses as more benign, particularly given the document says the task force doesn't have consensus on how the APIs should be handled.
<dd> | ||
Web APIs that were designed to support users' immediate goals, like <a | ||
data-cite="dom#interface-event">DOM events</a> and <a | ||
data-cite="cssom-view-1#extension-to-the-element-interface">element position | ||
observers</a>. | ||
</dd> | ||
|
||
<dt><dfn>Ancillary APIs computed from existing information</dfn></dt> | ||
<dt><dfn>Supporting APIs computed from existing information</dfn></dt> |
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.
Unrelated to the change being made in this PR, but I find the "Supporting APIs computed from existing information" phrasing a bit strange (what's a "computed API"?) How about something like "Supporting APIs that provide derived information"?
Another approach might be "primary" vs "secondary" instead of "non-ancillary" and "ancillary". Or maybe "primary" and "auxiliary"? |
Preview | Diff