- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jan 2016 19:30:16 +0000
- To: public-web-bluetooth-log@w3.org
Specs are full of descriptions that don't match the implementations
exactly. https://tc39.github.io/ecma262/#sec-map-objects has a good
example, where it's specified in terms of a linear search to describe
the external behavior, but also requires sublinear access. We
shouldn't diverge where it doesn't make the specification simpler, but
in this case, I think organizing the information a UA has to remember
about a device into {whole-UA, per-origin, per-window} does make it
easier to understand. I don't think it diverges too much from the
implementation, either: even if you map from internal-id to
web-visible-id, and then from that id to the origin, the allowed
servers, and the internal-id, it's recognizable as the same
information as the spec wants.
So I'm not inclined to change this in the spec unless there's a
concrete proposal that makes it easier to understand.
--
GitHub Notification of comment by jyasskin
Please view or discuss this issue at
https://github.com/WebBluetoothCG/web-bluetooth/issues/199#issuecomment-174630219
using your GitHub account
Received on Monday, 25 January 2016 19:30:21 UTC