- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 26 Mar 2014 13:00:17 -0700
- To: Dan Burnett <dburnett@voxeo.com>
- Cc: Harald Alvestrand <harald@alvestrand.no>, Jan-Ivar Bruaroey <jib@mozilla.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 26 March 2014 12:51, Dan Burnett <dburnett@voxeo.com> wrote: > I don't remember who suggested it, but at TPAC there was a suggestion to allow values (not properties, values) for all types that would represent "the highest possible" and "the lowest possible". This is an interesting example of a completely orthogonal addition that trivially addresses the use case of "give me the highest value you can", without having to add another attribute such as ideal that only hints at what the user might actually want. Several people did separately, as I recall. (The mailing list archives should show several examples.) The problem with overloading the value space in this way is that it is less semantically clean. Jan-Ivar's proposal here seems like it can handle the use cases well enough. (If you want to get fancy, Number.POSITIVE_INFINITY stands well for "highest")
Received on Wednesday, 26 March 2014 20:00:47 UTC