[w3c/IndexedDB] Simplify transaction starting constraints to match reality (#319)

All implementations have a strict ordering of transactions with
overlapping scopes; read-only transactions can run in parallel but
block a later read/write transaction from starting, and the read/write
transactions similarly block later read/write and read-only
transactions.

Tighten up the constraints definition to something precise, and move
the wordy implications into a non-normative aside.

Also, define "overlapping scopes" as a term.

Closes #253

Closes #???

The following tasks have been completed:

 * [ ] Confirmed there are no ReSpec/BikeShed errors or warnings.
 * [ ] Modified Web platform tests (link to pull request)

Implementation commitment:

 * [ ] WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
 * [ ] Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=)
 * [ ] Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/IndexedDB/pull/319

-- Commit Summary --

  * Simplify transaction starting constraints to match reality

-- File Changes --

    M index.bs (91)

-- Patch Links --

https://github.com/w3c/IndexedDB/pull/319.patch
https://github.com/w3c/IndexedDB/pull/319.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/w3c/IndexedDB/pull/319