[whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537)

As it relates to the fetching algorithm, the term "basic" is sub-optimal
for a number of reasons:

- It implies a relative level of simplicity. Because the algorithm
  includes an invocation of HTTP Fetch, it is conceptually more complex
  than most other fetching algorithms defined in the specification.
- It suggests a relationship to the "basic" request tainting value and
  "basic" filtered response. While the algorithm is invoked for requests
  whose tainting is "basic", it is also invoked for requests whose
  tainting is set to "opaque".

Re-name the algorithm to "generic fetch" in order to more precisely
describe its high-level nature while avoiding association with any
particular request tainting value.

---

@annevk I'm probably only thinking along these lines because of my inexperience
with the specification, but I know that same inexperience makes it easier for
me to stomach vocabulary changes like this. These details certainly have
momentum for folks who have been working in this space for a while. My bias
notwithstanding, I do think this would make the text easier to follow. Other
alternatives that would address my concern are "scheme fetch" or "scheme-based
fetch", though those may be too technical/wordy.
You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/537

-- Commit Summary --

  * Editorial: rename "basic fetch" to "generic fetch"

-- File Changes --

    M fetch.bs (8)

-- Patch Links --

https://github.com/whatwg/fetch/pull/537.patch
https://github.com/whatwg/fetch/pull/537.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/537