W3C home > Mailing lists > Public > public-media-capture@w3.org > April 2014

Re: [Bug 22593] Capabilities are buggy

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 03 Apr 2014 11:21:00 +0200
Message-ID: <533D27FC.3050601@alvestrand.no>
To: public-media-capture@w3.org
(continuing actual discussion on list, since it clutters up bugzilla)

On 04/03/2014 11:14 AM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22593
> --- Comment #4 from Dominique Hazael-Massieux <dom@w3.org> ---
> Makes sense; so that leaves the question of the meaningfulness of having an
> array of values for facingMode in capabilities.
> In particular, the example in 11.3 has:
>    facingMode": ["user", "environment"]
> which doesn't make sense to me; it may be that there is some (obsolete?)
> ambiguity about whether capabilities are at the UA level (which the text in
> 11.3 seems to imply) or at the source level.
No, I think you're misreading the semantics here.
This will match all devices that have facingMode either user or environment.
Each camera can only have a single value for facingMode, but it makes
perfect sense to say that multiple values for facingMode are acceptable.

A more realistic example would probably be ["user", "left", "right"] -
as in "give me any camera that faces in the direction of the user, and
not the opposite way".

We don't have a "not" operator in the capabilities (either the previous
or the current proposal).

So can I close this bug as "fixed"?

Surveillance is pervasive. Go Dark.
Received on Thursday, 3 April 2014 09:21:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:25 UTC