W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2022

Re: Call for Consensus (CfC) to publish a FPWD of "Capture Handle - Bootstrapping Collaboration when Screensharing".

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Tue, 5 Apr 2022 19:02:16 -0400
Message-ID: <CABr+gEgsmoqr2E1YZb0iZhgKrr6_doF4E2B3TUSTMkG9kvyVUA@mail.gmail.com>
To: "public-webrtc@W3.org" <public-webrtc@w3.org>
Cc: Bernard Aboba <Bernard.Aboba@microsoft.com>
I object to publishing a Capture Handle (identity) FPWD, due to issues
filed in #11 and #12.

There’s disagreement in #11 over whether setCaptureHandleConfig, as
defined, is too powerful: it is meant to be a bootstrap for a cross-origin
messaging channel, not be one itself. If implemented as-is, my concern is
applications might immediately become dependent on its side-effects, since
misusing it as a local messaging channel seems simpler than its designed
purpose (setting up e.g. a RESTFUL api to reach cross-origin) in many cases.

There’s disagreement in #12 over API shape, whether getCaptureHandle()
belongs on the track. Tracks are designed to be cloned and even transferred
to workers. It seems undesirable that a cross-origin messaging channel be
given to all media consumers. Instead, a dedicated CaptureController object
that is neither cloneable nor transferable seems a superior location, to
separate control (affecting all tracks) from consumption of a single track.

The reader of the FPWD should be made aware of these outstanding issues in
the document itself.

The process [1] states:

*"For all Working Drafts a Working Group:*

   - *should** document outstanding issues, and parts of the document on
   which the Working Group does not have consensus, and *
   - *may** request publication of a Working Draft even if its content is
   considered unstable and does not meet all Working Group requirements."*

Assuming there are no other objections, my objection can be resolved by
documenting the above lack of consensus as Notes in the document itself,
like we recently did for Region Capture.

[1] https://www.w3.org/2020/Process-20200915/#maturity-levels
[11] https://github.com/w3c/mediacapture-handle/issues/11
[12] https://github.com/w3c/mediacapture-handle/issues/12

On Tue, Mar 22, 2022 at 7:15 PM Bernard Aboba <Bernard.Aboba@microsoft.com>

> This is a Call for Consensus (CfC) to publish a First Public Working Draft
> (FPWD) of "Capture Handle - Bootstrapping Collaboration when
> Screensharing".
> The document is available for inspection here:
> https://w3c.github.io/mediacapture-handle/identity/index.html
> The github repo is here:
> https://github.com/w3c/mediacapture-handle
> In response, please state one of the following:
>   *   I support publishing a FPWD of the Capture Handle (identity)
> specification
>   *   I object to publishing a Capture Handle (identity) FPWD, due to
> issues filed in open bug <#number>
> The CfC will end on April 6, 2022.
> Bernard
> For the Chairs

.: Jan-Ivar :.
Received on Tuesday, 5 April 2022 23:03:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 April 2022 23:03:42 UTC