- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Thu, 31 Oct 2013 00:20:57 +0900
- To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
- Message-ID: <CAJ8iq9WLYwdfEhmKKUHemQ4cyv_yF7=sAztor=cjHi=cJ38u9A@mail.gmail.com>
available at:
http://www.w3.org/2013/10/30-webtv-minutes.html
also as text below.
Thanks,
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Web&TV IG - Media APIs TF meeting
30 Oct 2013
[2]Agenda
[2] http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0063.html
See also: [3]IRC log
[3] http://www.w3.org/2013/10/30-webtv-irc
Attendees
Present
Paul, SunHei, Kaz, Bin, Giri, Daniel, Hyun, Louay,
Yosuke, Igarashi, Olivier
Regrets
Mark, JC
Chair
bin
Scribe
kaz
Contents
* [4]Topics
1. [5]Action items
2. [6]Review of gap analysis
3. [7]TPAC
* [8]Summary of Action Items
__________________________________________________________
bin: checking the participants
... Olivier sent out the agenda
... will check the actions
Action items
<Bin_Hu> [9]http://www.w3.org/2011/webtv/track/products/7
[9] http://www.w3.org/2011/webtv/track/products/7
action-125?
<trackbot> action-125 -- Giuseppe Pascale to Draft use cases
related to metadata -- due 2013-11-21 -- OPEN
<trackbot> [10]http://www.w3.org/2011/webtv/track/actions/125
[10] http://www.w3.org/2011/webtv/track/actions/125
bin: still open
action-153?
<trackbot> action-153 -- Giridhar Mandyam to Look through
webrtc column in gap analysis document -- due 2013-10-30 --
PENDINGREVIEW
<trackbot> [11]http://www.w3.org/2011/webtv/track/actions/153
[11] http://www.w3.org/2011/webtv/track/actions/153
bin: seems it's done
... right?
giri: yep
close action-153
<trackbot> Closed action-153.
action-154?
<trackbot> action-154 -- Sheau Ng to Look through web storage
column in the gap analysis doc -- due 2013-11-13 -- OPEN
<trackbot> [12]http://www.w3.org/2011/webtv/track/actions/154
[12] http://www.w3.org/2011/webtv/track/actions/154
bin: for Sheau
... Web Storage
... seems finished
close action-154
<trackbot> Closed action-154.
action-156?
<trackbot> action-156 -- Bin Hu to Look through server-sent
events columns in gap analysis doc -- due 2013-10-23 -- OPEN
<trackbot> [13]http://www.w3.org/2011/webtv/track/actions/156
[13] http://www.w3.org/2011/webtv/track/actions/156
bin: done
close action-156
<trackbot> Closed action-156.
action-157?
<trackbot> action-157 -- Bin Hu to Look through push api column
in gap analysis doc -- due 2013-10-23 -- OPEN
<trackbot> [14]http://www.w3.org/2011/webtv/track/actions/157
[14] http://www.w3.org/2011/webtv/track/actions/157
bin: done
close action-157
<trackbot> Closed action-157.
action-158?
<trackbot> action-158 -- Sheau Ng to Look through
manifest/appcache column, to be used as input for service
worker -- due 2013-11-13 -- OPEN
<trackbot> [15]http://www.w3.org/2011/webtv/track/actions/158
[15] http://www.w3.org/2011/webtv/track/actions/158
bin: for Sheau
... Manifest
... manifest is done
... appcache needs reorganization
... no appcache spec
... so action itself is done
close action-158
<trackbot> Closed action-158.
action-161?
<trackbot> action-161 -- Louay Bassbouss to Review indexed
database api for media apis gap analysis -- due 2013-11-13 --
PENDINGREVIEW
<trackbot> [16]http://www.w3.org/2011/webtv/track/actions/161
[16] http://www.w3.org/2011/webtv/track/actions/161
bin: in progress?
louay: think we can review later
... basically finished from my side
close action-161
<trackbot> Closed action-161.
action-162?
<trackbot> action-162 -- Sung Hei Kim to Review File API & File
API: Writer for Media APIs gap analysis -- due 2013-11-13 --
OPEN
<trackbot> [17]http://www.w3.org/2011/webtv/track/actions/162
[17] http://www.w3.org/2011/webtv/track/actions/162
bin: Sung Hei?
skim13: done
close action-162
<trackbot> Closed action-162.
bin: we need to review the result
action-163?
<trackbot> action-163 -- Yosuke Funahashi to Review web crypto
api for media apis gap analysis -- due 2013-11-13 -- OPEN
<trackbot> [18]http://www.w3.org/2011/webtv/track/actions/163
[18] http://www.w3.org/2011/webtv/track/actions/163
bin: Yosuke?
yosuke: still working
... will finish this week
bin: ok
... are there any missing pieces?
... media source extension is done by Olivier
... encrypted media extension is ongoing
... that is the current status
Review of gap analysis
bin: NSD API
... 3 features on device discovery are covered
... 5 red ones are not covered
... 3 yellow ones are not sure
... next is "HTML5"
... 1.22 Content Playback is covered
... 3 features need further investigation
... "HTML 5.1"
... 1.16 Tuner Control is not covered yet
... who did this review?
... 1.23 Content Recording while Watching is not covered
giri: not sure who did this
... but guess the logic (why not covered by 5.1) would be
supported by WebRTC instead of HTML 5.1
bin: ok
kaz: should we record that point on the spleadsheet itself?
bin: can try
kaz: maybe you can insert a new column between A and B?
bin: (adding comments)
... next "WebRTC"
... 3 features covered
... 2 features not covered but should be covered
... 4 features need further discussion
... and "Web Storage"
... 2 features covered
... 1.5.1 Device Authentication Mechanism is not covered but
should be
... 4 features need further discussion
... move on to EME
... 3 requirements covered
... 1.20 Media Content Protection (Offline) needs further
discussion
... next "File API"
... 2 requirements covered
... 4 requirements need further investigation
... any comments/questions?
... move on to "File API: Writer"
... 4 covered
... 3 need further investigation
... next "Indexed DB"
(Olivier just joined)
bin: (explains the situation)
... looking at the google doc table
... added a comment on COntent Recording while Watching
olivier: ok
bin: "Indexed DB"
... 5 features covered
... 6 items need further investigation
... comments?
<olivier>
[19]http://lists.w3.org/Archives/Public/public-web-and-tv/2013O
ct/0065.html
[19] http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0065.html
olivier: just saw the comment on MSE
louay: DB API is generic api for storage
... not sure about service synchronization mechanism, etc.
bin: agree Indexed DB is a generic API for storage
... and needs further investigation
... for some requirements implemented two or more specs could
be combined
... maybe good for requirements description
kaz: in that case, maybe we might want to add another comment
on that to the spleadsheet?
bin: ok
... next Media Source Extensions
... "Push API"
... synchronization and transfer should be covered
... push notification is not covered but needed
... wake-up mechanism needs further investigation
... questions?
... "Messaging API" by Sheau
... 2 requirements covered
... 1 needs further investigation
bin: let's assign an action item
... rationale for his analysis
[ Sheau is joining shortly. ]
olivier: can talk with Sheau about his rationale
kaz: is also interested in his rationale
bin: "Server-Sent Events"
... server can send any kind of events to web apps
giri: what we use this?
... WebSocket can be used
bin: two approaches
giri: I know
<olivier> worth adding web sockets column next to SSE?
<kaz> +1
giri: but not sure why WebSocket is not included
bin: Giri has just made a good point
... we can add WebSocket as well
olivier: agree
ddavis: +1
bin: we all agree then
... so who would like to do gap analysis?
giri: will do
<skim13> +q
<scribe> ACTION: gmandyam to do gap analysis for websocket
[recorded in
[20]http://www.w3.org/2013/10/30-webtv-minutes.html#action01]
<trackbot> Created ACTION-164 - Do gap analysis for websocket
[on Giridhar Mandyam - due 2013-11-06].
(Sheau has just joined)
bin: want to ask Sheau about Messaging API
sheau: messaging API was primarily text exchange
... focusing on part of the requirements
... thought device transfer could be covered
... maybe smarter than handling device itself
skim13: should also look at the gap on Device APIs and SysApps
APIsw
kaz: agree
... though they're trying many new APIs
-> [21]http://www.w3.org/2012/sysapps/ SysApp work
[21] http://www.w3.org/2012/sysapps/
kaz: wondering if we would concentrate on API definition or
might wan to see generic message handling architecture as well
bin: good question
... APIs might be compatible with that architecture
kaz: maybe we should concentrate on APIs first and can see
extension later
sheau: some of our requirements are horizontal
... while others should be considered deeper
... e.g., tuner control should be considered deeper
... some architecture or picture might give clearer view
... but it may force us much work
bin: yeah, it may make our work a long journey
... we have already done much work
... we'd like to get a consolidated view at TPAC
... e.g., WebSocket is not yet analyzed yet
... maybe we can see what would be the best approach after
finishing the current gap analysis
... we can talk about that at TPAC
kaz: agree
... and we can visit the meetings of related groups, can't we?
bin: is it possible to have a joint meeting with MMI?
kaz: yes, we (web&tv ig) can hold a joint meeting with MMI
... also I'd suggest we hold joint meetings with the other
related groups as well
<scribe> ACTION: kaz to ask the MMI WG about a joint meeting
with web&tv ig [recorded in
[22]http://www.w3.org/2013/10/30-webtv-minutes.html#action02]
<trackbot> Created ACTION-165 - Ask the mmi wg about a joint
meeting with web&tv ig [on Kazuyuki Ashimura - due 2013-11-06].
bin: "Manifest"
giri: service expiry mechanism not covered
... 4 features need further investigation
bin: web crypto is ongoing
... who would like to do Service Worker?
giri: we can come back later
<olivier> +1
bin: (put a comment)
... we'll have another column on WebSocket
TPAC
olivier: TPAC is approaching
... we should decide what we would like to report there
... and aside question is
... who from this TF will be there
(we checked attendance)
olivier: make sure to get your VISA
bin: seems many participants there
... regarding the TF report
... we can talk about the gap analysis results
... coverage of our requirements
... and some discussion on an expected system architecture
... which pieces are missing
kaz: maybe providing WebEX service might be useful?
bin: yeah
olivier: regarding the agenda, like Bin's idea
... and would add 2 things
... 1. communication with the other groups based on the gap
analysis
... 2. and good opportunity to think about what kind of NEW
(non-existing) specs needed to fill the gap
... TPAC is a good opportunity to do that
bin: great suggestion
kaz: which groups do we want to meet?
olivier: not clear yet
kaz: maybe we can send a heads-up to the groups chairs and
staff contacts?
olivier: sure
kaz: ddavis and I will do that
<scribe> ACTION: kaz to work with Daniel and send a heads-up to
the related groups' chairs/team contacts [recorded in
[23]http://www.w3.org/2013/10/30-webtv-minutes.html#action03]
<trackbot> Created ACTION-166 - Work with daniel and send a
heads-up to the related groups' chairs/team contacts [on
Kazuyuki Ashimura - due 2013-11-06].
bin: will discuss those points at TPAC
[ adjourned ]
Summary of Action Items
[NEW] ACTION: gmandyam to do gap analysis for websocket
[recorded in
[24]http://www.w3.org/2013/10/30-webtv-minutes.html#action01]
[NEW] ACTION: kaz to ask the MMI WG about a joint meeting with
web&tv ig [recorded in
[25]http://www.w3.org/2013/10/30-webtv-minutes.html#action02]
[NEW] ACTION: kaz to work with Daniel and send a heads-up to
the related groups' chairs/team contacts [recorded in
[26]http://www.w3.org/2013/10/30-webtv-minutes.html#action03]
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [27]scribe.perl version
1.138 ([28]CVS log)
$Date: 2013-10-30 15:19:47 $
[27] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[28] http://dev.w3.org/cvsweb/2002/scribe/
--
Kaz Ashimura, W3C Staff Contact for Web&TV, MMI and Voice
Tel: +81 466 49 1170
Received on Wednesday, 30 October 2013 15:21:31 UTC