- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Feb 2015 15:31:48 +0000
- To: public-media-capture-logs@w3.org
The fitness distance algorithm conflates two things (and the spec is
better for it imho): 1) weeding out sources that don't meet required
constraints, and 2) scoring finite sources against an ideal.
Therefore, advanced must be part of the algorithm. I don't see a flaw
in the SelectSettings() algorithm other than that it could be a lot
clearer about that finite distances in step 5 are not to be used for
anything.
That's why this PR suggests adding the text it does ("The UA SHOULD
use the one with the smallest <code>fitness distance</code>**, as
calculated in step 3**.")
--
GitHub Notif of comment by jan-ivar
See
https://github.com/w3c/mediacapture-main/pull/126#issuecomment-74883603
Received on Wednesday, 18 February 2015 15:31:59 UTC