- From: Yosuke Funahashi <yosuke@w3.org>
- Date: Thu, 21 Jan 2016 16:01:50 +0900
- To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
available at:
https://www.w3.org/2016/01/20-webtv-minutes.html
also as text below.
Yosuke
--
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Web+TV Cloud Browser TF teleconf
20 Jan 2016
See also: [2]IRC log
[2] http://www.w3.org/2016/01/20-webtv-irc
Attendees
Present
Mark_Vickers, Andrzej_Zawadzki, Bill_Rose, Bob_Lund,
Bryan_Sullivan, Oliver_Friedrich, Alexandra_Miktyuk,
Kasar_Masood, Chris_Needham, Colin_Meerveld, Dan_Druta,
Louay_Bassbouss, Stefan_pham, Joe_Steele, Nilo_Mitra,
Ronen_Mizrahi, Yosuke_Funahashi, Francois_Daoust,
Kaz_Ashimura
Regrets
Chair
Alexandra
Scribe
Yosuke
Contents
* [3]Topics
1. [4]Self introductions
2. [5]IG introduction and TF background
3. [6]Communication: regular call
* [7]Summary of Action Items
* [8]Summary of Resolutions
__________________________________________________________
Self introductions
Alex: Let's get started.
... We're now launching the CBTF.
... We had a discussion about this launch at TPAC, Sapporo,
... as well as presentaions on this topic.
... Let's start from self-introductions.
... Oliver, my colleague is here.
Oliver: We have a long history on this tech
... and think W3C is the best plece to standardise it.
... We had some preliminary discussion at Sapporo.
... Ex. EME and MSE is likely to need some modification to be
used on cloud browsers.
... Some other ongoing W3C work might need some modifications.
Mark: I'm one of the co-chairs of the IG with Giuseppe and
Yosuke.
Nilo: I'm from Ericson, joining TV Control API work.
BobLund: From CableLabs. Worked on HTML WG texttracks.
joesteele: from Adobe. Works on EME and MSE
Chris: I'm from BBC, joining TV Control API and the IG.
Dan: I'm joining WebRTC.
Bryan: from ATT.
Colin: from ActiveVideo working on Cloud Browser. An Invited
Expert.
Glenn: from NBCU, working on GGIE.
Louay: from Fraunhofer.
Andrzej: from Opera Software
Ronen: From TVersity, working on Cloud Browser techs.
IG introduction and TF background
Mark: Thanks a lot for your introductions.
... I'd like to give you some basic information of the IG
... and some backgournd of the TF.
... Yosuke or Kaz, can you put the email address of the chairs
list?
<yosuke> team-webandtv-chairs@w3.org
<kaz> above is the ML of the Web&TV IG co-Chairs
Mark: If you have any questions, please send it to this
relfector.
... Now, let me introduce the task force.
... It's a really good time to start cloud browser work.
... One important characteristic of the IG is that
... IG focuses on use cases and requirements.
... We don't do tech works here.
... We pass our requests to other WGs if something should be
standardised.
... So, the TF's goal is to create clear requirement docs.
... We have some online tools/spaces, reflector, wiki, and
github.
... The reflector is a good place to interact.
... Please use [Cloud Browser] prefix for this discussion. ...
The ML is completely public.
Mark: The IG wiki is also public:
[9]https://www.w3.org/2011/webtv/wiki/Main_Page
... Each TF has its own area.
... Now GGIE and CB have theirs.
... The wiki also contains information of past TFs.
... You can check what they achived there.
... Ex. The Media pipeline TF's work resulted in MSE and EME.
... This is a good example of what this CBTF should achive.
[9] https://www.w3.org/2011/webtv/wiki/Main_Page
<yosuke> [10]Media Pipeline Task Force
[10] https://www.w3.org/2011/webtv/wiki/MPTF
<yosuke> [11]MPTF Requirements for Adaptive Bit Rate Streaming
[11] https://dvcs.w3.org/hg/webtv/raw-file/tip/mpreq/adbreq.html
<kaz> [12]Home Network TF Requirements Note
[12] https://www.w3.org/TR/hnreq/
Mark: You start from use cases,
... proceed to requirement,
... which results in real tech works like MSE and EME.
... Next step will be
... presenting it to the WGs
... or creating a CG like we did for TV Control API.
... CG is an interesitng opition.
... There is a WICG.
<kaz> [13]TV Control API CG
[13] https://www.w3.org/community/tvapi/wiki/Main_Page
Mark: it's also an interesting option as a destination.
<kaz> [14]TF participants
[14]
https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Cloud_Browser_TF_Participants
Mark: Please put your name on the CBTF wiki.
... There is a page to register participants.
... That said, I'd like to hand over the control of the meeting
to Alexandra.
Mark: We are pretty impressed by the presentations in TPAC
Sappro.
... Before I leave I'd like to take questions if you have.
Alexandra: I have two questions.
<alexandra_mikityuk>
[15]https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_
TF/UseCases
[15] https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases
Alexandra: I've created a use case template page.
... Is it okay to gather use cases with this at the beginning
... And finish with the wrap-up doc like MPTG?
Mark: Right.
... In case of the MPTF, they used wiki as well before they
started writing the final doc.
... BTW, one thing I forget to mention is
... conf calls and f2f meetings are only for W3C members.
... IE status could be given during you are considering W3C
membership.
... The reason of this is that we need W3C staff resouce to
make our work proceed.
Alexndra: The next question is,
... from the MSE and EME perspective,
... how we can/should involve browser vendors?
... Should we start interacting at WICG from now?
Mark: Good question.
... Affecting browser vendors is the key point of works in W3C.
... My suggestion is
... to start socializing your ideas with browser vendor guys.
Bryan: This is browsers on cloud.
... so invoving browser vendors is definitely important.
... At the same time, we might have other types of browser
vendors for this,
... because it's running on cloud. I mean browser vendors
... other than the major browser vendors.
Communication: regular call
Alexandra: Thanks Mark.
... Let's move on to next item.
... We'll dig into use case on the next call.
... Let's talk about organizational point.
... 1) Frequency of regular call
... 2) date and time slot for it
... Shoud we decide it on the call or do it by using Doodle?
... BTW, my motivation in this group is that
... we've struggled for a long time on this tech.
... One difficulty was that this tech was a nitch market.
... Hope the TF will work to let us get more implementations.
... The second thing is that
... Some new parties seem like interested in this work
... ex. Hulu and Massive Interactive.
... Also we're intersted in standarsizing globaly on this
topic.
... Happy to have ActiveVideo and TVersity on this call.
... Not sure why Entrix from South Korea is not on this call.
<bryan> the key point I was making (sorry for speaking so
fast), is that the concept being discussed here is really a new
type of web user agent, while similar in some ways to what
Opera has offered since Mini, it really a cloud application
with a (presumably) slim user-device-side component. Thus we
are likely to see more implementations beyond the "big 5"
<bryan> browsers, e.g. media device vendors and even service
providers. So we should encourage them to also participate, as
with the traditional user agent vendors.
Alexandra: So we have alrady three implementors.
... Let's listen to two implementors' self-introductions.
Ronen: Our product is Cloud Browser calld tversity
... It recently adopted by Dish.
... Cloud Browser has a potential
... to achive isolate app from client terminal
... it has new posibility about privacy and security.
Alexandra: Thanks. Colin?
Colin: ActiveVideo techs enables legacy boxes create
... very smooth UIs
... as well as for new tech like HDMI sticks.
Alexandra: Thanks.
... We have a good relationship with thsese companies on R&D.
... I'll also contact Entrix later.
Alexandra: About use cases:
... I expect we can gather use cases from various parties, I
mean not only from telcos.
Kaz: sorry but need to ask for clarification from the W3C
procedure viewpoint. Ronen is a one time guest invited by you
as the TF moderator, right?
Alex: yes.
Kaz: We identify that kind of guest at the begining of a call.
Alex: Understood. Thanks.
... Let's go back to the discussion on our regular call slot.
... How about starting with weekly and see we have enought
topics
... and make it more infrequesnt if appropriate.
Oliver: Currently the use cases are TV centric
<kasar> good start weekly
Oliver: but we might have other perspective on CB.
... So, starting from weekly would work fine to see such new
perspective asap.
Alex: Any comments? ... I see no objections.
... So, let's go with weekly calls.
Alex: Please start submitting use cases on the wiki page.
Mark: if you have any questions or issues to submit your ideas
on the wiki, please let me know.
Alex: AOB?
... [Nothing from participants]
... See you next week!
... [Adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [16]scribe.perl version
1.144 ([17]CVS log)
$Date: 2016/01/21 06:59:23 $
[16] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[17] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 21 January 2016 07:01:59 UTC