- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 20 Jan 2016 15:15:34 +0000
- To: Harald Alvestrand <harald@alvestrand.no>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
> On 20 Jan 2016, at 15:06, Harald Alvestrand <harald@alvestrand.no> wrote: > > At the Sapporo meeting, we had a presentation on depth tracks and > mediachannel-worker (with most of the presentation time given to > mediachannel-worker). > > Our various charters can reasonably be read to say that we should take > care of stuff that can be captured analogously with audio and video - > thus depth was originally agreed to be in-scope, but not more important > than our first set of deliverables - but whether we're the right home > for the "mediaworker" project seems like a more unclear topic. > > This note is intended to solicit opinions, given that our > mediacapture-main work seems to be closing in on completion: Happy to see mediacapture-main advance toward completion. Congrats to the folks actively contributing to the spec and implementations over the years! > - Should we (continue to) adopt mediacapture-depth as a TF item? > - Should we adopt the proposed mediacapture-worker as a TF item? Yes. I believe this TF continues to be the best home for these deliverables while the Timed Media WG is in the making. Longer term the Timed Media WG was envisioned as the home for these as well as other audio and video related deliverables beyond mediacapture-main. > - What, if anything, needs to be done to our charters (TF, DAP and > WEBRTC) to make sure the work is clearly within the WG's scope? The revised DAP WG (renamed to Device and Sensors WG) charter [1] under review [2] explicitly enumerates the mediacapture-depth and mediacapture-worker as deliverables to be worked on "in collaboration with the WebRTC Working Group". Given that, I believe the only thing that needs to be done is to get the revised DAP/DAS WG charter approved, since the TF deliverables are covered by the union of RF commitments for both groups, as stated in the current TF charter [3] (linked from [4]). Thanks, -Anssi [1] https://www.w3.org/2015/11/DeviceSensorsCharter.html#deliverables [2] https://lists.w3.org/Archives/Public/public-device-apis/2016Jan/0005.html [3] https://lists.w3.org/Archives/Public/public-media-capture/2013Feb/0012.html [4] https://www.w3.org/wiki/Media_Capture
Received on Wednesday, 20 January 2016 15:16:07 UTC