Re: Call for Consensus (CfC) on Issue 17 of "Region Capture"

CropTarget production should be asynchronous.


(If you have already read all the arguments, you can stop reading here, 
it's a repetition.)


The only existing implementation of this API requires an asynchronous 
API, and requiring the API to be synchronous would invalidate this design.


Given that there is no working synchronous implementation of the API, 
and even if there were, it is impossible to verify that this would lead 
to an appropriate design for that environment, forcing synchronous is 
inappropriate.


Supporting an asynchronous API on top of architectures where a 
synchronous API is the simpler design is trivial; in the other 
direction, it is not.




On 7/12/22 09:34, Bernard Aboba wrote:
> This is a Call for Consensus (CfC) on Issue 17 of "Region Capture".
>
> Section 6.2 of the "Region Capture" specification contains a Note:
>
> image.png
>
> Issue 17 of "Region Capture" is available here:
> What makes CropTarget special to require an asynchronous creation? · 
> Issue #17 · w3c/mediacapture-region · GitHub 
> <https://github.com/w3c/mediacapture-region/issues/17>
>
> The Discussion of Issue 17 at the June 23 Virtual Interim is available 
> here:
> WEBRTCWG-2022-06-23 - Google Slides 
> <https://docs.google.com/presentation/d/1-SgzfMAeVG3u5vErJncC7OKDTGNDzSOMg_78LP8SULk/edit#slide=id.g131149eddb2_0_0>
>
> Minutes of the June 23 Virtual Interim are here:
> https://www.w3.org/2022/06/23-webrtc-minutes.html 
> <https://www.w3.org/2022/06/23-webrtc-minutes.html>
>
> In replying to this CfC, respondents should indicate one of the following:
>
> * CropTarget production should be synchronous.
> * CropTarget production should be asynchronous.
>
> The CfC will last until July 26, 2022 at midnight Pacific Time.
>
> Bernard
> For the Chairs
>