12:58:48 RRSAgent has joined #webtv 12:58:48 logging to http://www.w3.org/2013/10/02-webtv-irc 12:59:19 ddavis has joined #webtv 12:59:27 zakim, call kazuyuki-617 12:59:27 sorry, kaz, I don't know what conference this is 13:00:10 zakim, this will be webtv 13:00:10 ok, kaz, I see UW_WebTVIG()9:00AM already started 13:00:13 zakim, call kazuyuki-617 13:00:13 ok, kaz; the call is being made 13:00:14 +Kazuyuki 13:00:23 zakim, who is here? 13:00:23 On the phone I see ??P6, Kazuyuki (muted) 13:00:24 On IRC I see ddavis, RRSAgent, Zakim, giuseppep, skim13, igarashi, kaz, silvia, trackbot 13:00:30 +[IPcaller] 13:00:37 Zakim, ??P6 is ddavis 13:00:37 +ddavis; got it 13:00:47 zakim, IPcaller is giuseppe 13:00:47 +giuseppe; got it 13:00:48 Bin_Hu has joined #webtv 13:01:03 gmandyam has joined #webtv 13:01:07 zakim, who is here? 13:01:07 On the phone I see ddavis, Kazuyuki, giuseppe 13:01:08 On IRC I see gmandyam, Bin_Hu, ddavis, RRSAgent, Zakim, giuseppep, skim13, igarashi, kaz, silvia, trackbot 13:01:15 + +1.858.750.aaaa 13:01:23 Zakim, aaa is gmandyam 13:01:23 sorry, gmandyam, I do not recognize a party named 'aaa' 13:01:30 Zakim, aaaa is gmandyam 13:01:30 +gmandyam; got it 13:01:49 Giri Mandyam from Qualcomm Innovation Center joining 13:01:50 olivier has joined #webtv 13:02:24 + +1.425.214.aabb 13:02:34 zakim, aabb is Bin 13:02:34 +Bin; got it 13:02:37 zakim, aabb is Bin_Hu 13:02:37 sorry, Bin_Hu, I do not recognize a party named 'aabb' 13:03:38 +??P14 13:03:49 zakim, ??P14 is igarashi 13:03:49 +igarashi; got it 13:03:57 igarashi has joined #webtv 13:04:39 + +1.818.406.aacc 13:06:04 zakim, aacc is cyril 13:06:04 +cyril; got it 13:06:54 olivier, are you joining? 13:07:44 agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2013Sep/0050.html 13:08:27 Chair: Bin 13:08:42 zakim, who is here? 13:08:42 On the phone I see ddavis, Kazuyuki, giuseppe, gmandyam, Bin, igarashi, cyril 13:08:44 On IRC I see igarashi, olivier, gmandyam, Bin_Hu, ddavis, RRSAgent, Zakim, giuseppep, skim13, kaz, trackbot 13:08:45 +??P19 13:09:07 zakim, ??P19 skim13 13:09:07 zakim, ??P19 is skim13 13:09:07 I don't understand '??P19 skim13', kaz 13:09:08 +skim13; got it 13:09:11 whyun has joined #webtv 13:09:38 zakim, who is here? 13:09:38 On the phone I see ddavis, Kazuyuki, giuseppe, gmandyam, Bin, igarashi, cyril, skim13 13:09:40 On IRC I see whyun, igarashi, olivier, gmandyam, Bin_Hu, ddavis, RRSAgent, Zakim, giuseppep, skim13, kaz, trackbot 13:10:07 agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2013Sep/0050.html 13:10:24 topic: Use cases 13:10:36 bin: deadline for use case discussion 13:10:39 CyrilRa has joined #webtv 13:11:04 +[IPcaller] 13:11:12 scribenick: ddavis 13:11:14 zakim, IPcaller is me 13:11:14 +olivier; got it 13:11:23 meeting: Media APIs TF meeting 13:11:28 +Mark_Vickers 13:11:35 zakim, who is here? 13:11:35 On the phone I see ddavis, Kazuyuki, giuseppe, gmandyam, Bin, igarashi, cyril, skim13, olivier, Mark_Vickers 13:11:37 On IRC I see CyrilRa, whyun, igarashi, olivier, gmandyam, Bin_Hu, ddavis, RRSAgent, Zakim, giuseppep, skim13, kaz, trackbot 13:12:29 Zakim, cyril is CyrilRa 13:12:29 +CyrilRa; got it 13:12:39 Mark_Vickers has joined #webtv 13:12:44 Zakim, Bin is Bin_Hu 13:12:44 +Bin_Hu; got it 13:13:17 giuseppe: We should finalise the use cases and decide which can be finished, and which can be deferred. 13:13:29 https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=0 13:13:38 -skim13 13:14:06 giuseppe: For Use Case 6, I'd like to go through the comments. 13:14:07 Present: Daniel, Kaz, Giuseppe, Giridhar, Bin, Igarashi, CyrilRa, SKim, WHyun, Olivier, Mark 13:14:12 +??P19 13:14:32 giuseppe: First is from me. 13:14:55 giuseppe: We often talk about a set-top box but we should include any type of tuner. This was agreed by the authors. 13:15:22 yes. we are in 13:15:24 giuseppe: Also, it shouldn't matter in the use case if you are a paid subscriber or not. 13:15:49 zakim, ??P19 is skim13,whyun 13:15:49 +skim13,whyun; got it 13:15:50 q+ 13:15:52 giuseppe: We should also cover any kind of application that wants to control the tuner, not just an EPG. 13:16:49 -olivier 13:16:55 gmandyam: When we talk about EPG being a web application, does it need to be accessible to the browser? Would it have to be retrievable by, e.g. XHR? 13:17:28 giuseppe: In the scope of this use case, it was intended to be a web page containing EPG data, not fetching it from the broadcast stream. 13:17:49 CyrilRa has joined #webtv 13:18:31 glenn has joined #webtv 13:18:51 Ooops, i thought that I've muted mic 13:18:53 whyun: Are you saying the web page contains the EPG data? A web page can have a list of channels available, but we were thinking of something broader. 13:19:07 -skim13,whyun 13:19:23 voip problem.. 13:19:33 +??P19 13:19:38 sorry.. we are in again 13:19:39 zakim, ??P19 is skim13,whyun 13:19:39 +skim13,whyun; got it 13:20:33 gmandyam, can you repeat the questions? 13:21:12 whyun: It's OK, we carry on and come back to questions later. 13:21:21 s/whyun/Bin_Hu/ 13:21:24 -CyrilRa 13:21:29 +[IPcaller] 13:21:32 zakim, IPcaller is me 13:21:32 +olivier; got it 13:21:48 zakim, who is here? 13:21:48 On the phone I see ddavis, Kazuyuki, giuseppe, gmandyam, Bin_Hu, igarashi, Mark_Vickers, skim13,whyun, olivier 13:21:50 On IRC I see glenn, CyrilRa, Mark_Vickers, whyun, igarashi, olivier, gmandyam, Bin_Hu, ddavis, RRSAgent, Zakim, giuseppep, skim13, kaz, trackbot 13:21:50 +CyrilRa 13:22:07 zakim, who is speaking? 13:22:18 kaz, listening for 10 seconds I heard sound from the following: ddavis (33%), gmandyam (47%), skim13,whyun (32%) 13:22:19 gmandyam: The use case doesn't say how the EPG data is made available to the web app. Is there an assumption that EPG data is retrievable through existing standards such as XHR, Web Sockets, etc.? 13:22:38 gmandyam: Because it could also come from broadcast streams. 13:23:14 giuseppe: The web page is designed to have that data included. It's probably not the focus of this use case but could be part of a metadata use case in future. 13:23:14 q+ to ask if "EPG data" should be unpacked as channel, programme id, timing etc? 13:23:23 ack gmandyam 13:23:35 giuseppe: So for now, EPG data is just some data that is part of the web app. 13:24:07 q? 13:24:10 ack o 13:24:10 olivier, you wanted to ask if "EPG data" should be unpacked as channel, programme id, timing etc? 13:24:22 olivier: EPG data seems too vague for our needs. Maybe it's better to specify it where possible, such as channel data, timing data, etc. 13:24:24 -skim13,whyun 13:24:27 CyrilRa_ has joined #webtv 13:24:51 giuseppe: We could use another term. What we're saying here is that a web app can tune into a channel and its data. 13:24:59 we are suffering from voip connection problem. sorry 13:25:01 olivier: but channel is only one part of EPG data. 13:25:15 +[IPcaller] 13:25:23 yes. we are joining using skype 13:25:25 giuseppe: So we need to rephrase this, if we have another suggestion. 13:25:30 we are in 13:25:32 Zakim, mute me 13:25:32 ddavis should now be muted 13:25:33 zakim, IPcaller is skim13,whyun 13:25:34 +skim13,whyun; got it 13:25:41 zakim, who is noisy? 13:25:52 kaz, listening for 10 seconds I heard sound from the following: giuseppe (60%) 13:26:02 giuseppe: Anyway, let's move on if there are no further suggestions. 13:26:26 Bin_Hu: So Giuseppe, will you edit the use case to make the phrasing a bit clearer? 13:26:40 "The TV broadcasting service provider (or third party service provider) provides application such as EPG which can provide mapping information of the TV channel." 13:26:44 giuseppe: The other has already clarified the wording so I'm happy to leave it as it is, with the comment. 13:26:53 (fine with me) 13:27:01 giuseppe: The rest of the use case is fine with me. 13:27:19 giuseppe: We don't need to use the word "installed" web application. 13:27:43 giuseppe: I think we go ahead with this. 13:28:00 giuseppe: Do we have an agreement on this? 13:28:19 skim13: Yes, we just wanted to see what you think of our suggestions. We will update the wiki. 13:28:24 giuseppe: Yes, I'm happy. 13:28:36 giuseppe: For Use Case 7 it was similar comments. 13:28:53 giuseppe: E.g. the subscriber issue, the general device, not just STB, etc. 13:29:17 rrsagent, make log public 13:29:22 rrsagent, draft minutes 13:29:22 I have made the request to generate http://www.w3.org/2013/10/02-webtv-minutes.html kaz 13:29:29 skim13: Do we agree, instead of using the word "set-top box" we use "device with tuner"? 13:29:53 giuseppe: Yes, either we use "device with tuner" everywhere, or we specify it once and then say "device" after that. 13:30:13 olivier: I think the second case is probably clearer 13:30:17 +1 13:30:41 giuseppe: So I propose "user-activated device with tuner" 13:30:52 skim13: I'll update use case 7 based on the comments. 13:30:52 assign actions? 13:31:05 ACTION: skim13 to update use cases 6 & 7 based on comments. 13:31:05 Created ACTION-146 - Update use cases 6 & 7 based on comments. [on Sung Hei Kim - due 2013-10-09]. 13:31:30 q+ to prioritise reqs, not ucs 13:31:41 giuseppe: I'd like to ask about the use cases - are we going to work with all of those on the page or split some off to the next iteration? 13:32:05 Bin_Hu: Not sure - what's your suggestion? 13:32:17 giuseppe: I don't think all of them have requirements - only up to use case 9 13:32:46 Zakim, unmute me 13:32:46 ddavis should no longer be muted 13:33:07 kaz has joined #webtv 13:33:22 ddavis: For example, use case 12 is potentially large so could be for a different iteration. 13:33:43 olivier: My suggestion is to keep the use cases but to prioritise based on the requirements. That where our main work is. 13:33:51 s/That/That's/ 13:34:11 giuseppe: We have limited time, so if we don't have the time to go through all the use cases, we could move them to the next iteration. 13:34:34 olivier: We've mostly done that already. We should look at the current list of requirements and see if we need to work on them or define them better. 13:34:38 Zakim, mute me 13:34:38 ddavis should now be muted 13:34:50 https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=0 13:34:58 giuseppe: But use cases 10, 11, 12 are not in the requirements doc. 13:35:11 olivier: You should be looking at the spreadsheet, that has the latest information. 13:36:08 olivier: We have a number of crosses for use cases 8 and 9. Who worked on that? Was that discussed already? 13:36:29 Bin_Hu: In the previous conf call, we decided to split Req 1.5 into several requirements. 13:37:16 olivier: Sheau is not on the call. It would be good to agree on this today to get rid of the red crosses and get it finalised. 13:37:41 olivier: Shall we go through the red crosses in the spreadsheet? 13:37:56 olivier: First is for Use Case 1 - Device discovery mechanism 13:38:45 olivier: I agree there is an element of device discover so I would say yes. No objections? 13:39:06 olivier: The bulk of issues are for use case 8 and 9, which both require authentication. 13:39:55 CyrilRa has joined #Webtv 13:39:59 olivier: Sheau's comment seems to be for any commercial service that requires authentication. So I would say yes to all six question marks. 13:40:35 Mark_Vickers: There is non-commercial use of these things as well. Commercial use is valid but there will be cases for using this without commercial interests as well. 13:40:45 olivier: Last was mutliscreen advertising. 13:41:25 olivier: Question was about device discovery mechanism so this is very close to use case 1. You have several devices discovering each other so I'd say this is also a "yes". 13:41:50 Zakim, unmute me 13:41:50 ddavis should no longer be muted 13:41:53 q+ 13:42:03 q- 13:42:25 q+ Bin_Hu 13:42:27 ack b 13:42:29 Bin_Hu: Some services running on a device can not be co-related. 13:42:42 giuseppe: It depends what a service is. 13:43:11 giuseppe: If you want to be generic, it doesn't really matter what is a service or a device. 13:43:19 ack ddavis 13:43:47 giuseppe: My impression was that if you say "service" you don't need to distinguish between service and device. 13:44:07 olivier: There's no use case where you'd one (e.g. service) and not the other (e.g. device). 13:46:08 giuseppe: People have UPnP in mind when thinking of this. There could be sub-services or sub-routines. 13:47:23 giuseppe: So the main requirement here is that we need an API to talk with another entity - another device, service, app, something. 13:47:37 olivier: So I think we can leave the requirements as they are for now. 13:47:52 Zakim, mute me 13:47:52 ddavis should now be muted 13:48:05 olivier: I think the main issue is 1. that we need to get this mapping back into the wiki. 13:48:37 olivier: How do we make sure we have one clear source for this mapping. I like the idea of a table but it may not be best to have a Google spreadsheet as our main source. 13:48:59 olivier: A proposal: I suggest we should remove the mapping from the use case document. 13:49:06 Zakim, unmute me 13:49:06 ddavis should no longer be muted 13:49:24 s/use case document/requirements document/ 13:50:10 giuseppe: With the table, we can keep it in a Google doc and later put all this in a HTML page. 13:50:35 ACTION: olivier to edit requirements doc to remove mapping and add a link to the Google spreadsheet. 13:50:35 Created ACTION-147 - Edit requirements doc to remove mapping and add a link to the google spreadsheet. [on Olivier Thereaux - due 2013-10-09]. 13:51:07 olivier: Next, how do we get from there to the gap analysis? Giuseppe - any experience to share from the Home Networking TF? 13:51:16 CyrilRa_ has joined #Webtv 13:51:33 giuseppe: I think we should go through the requirements and ask if there's a way to achieve this with existing specs. 13:51:51 giuseppe: If so, which ones and do they have partial or full coverage? 13:51:53 Zakim, cyrilra_ is CyrilRa 13:51:53 sorry, CyrilRa_, I do not recognize a party named 'cyrilra_' 13:52:04 i|Next|-> http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements Requirements document| 13:52:16 ddavis: This would require cooperation with other WGs 13:52:38 giuseppe: If we determine which WG is relevant for unmet requirements we can then contact them. 13:52:53 olivier: I'm not certain that going through them one-by-one is best. 13:53:09 olivier: I suggest people on this call look at the requirements and volunteer to take one each. 13:53:44 olivier: If each of use take one requirement and start looking at which technologies fulfil the requirement, if any, we can then come back to the group later. 13:53:53 Bin_Hu: Yes, we can divide the work. 13:54:14 olivier: If each person takes just one we can start small. 13:54:31 s/each of use/each of us/ 13:55:05 giuseppe: We could do it like that, or I don't have a problem going through the reqs seeing which is covered by e.g. the Network Service Discovery API (probably more than one). 13:55:07 q+ 13:55:28 Mark_Vickers: I think there's an advantage to having a discussion because it would increase everyone's knowledge. 13:55:51 Bin_Hu: Giuseppe probably has an overall idea already of which requirement is satisfied by which spec. 13:56:17 Bin_Hu: Maybe Giuseppe can take the first round quickly and see what is covered. Based on that we can narrow down the remaining requirements. 13:56:27 giuseppe: Yes, not all of them but some of them. 13:57:13 olivier: You mentioned the NSD API - are there other technologies that we should be aware of as big candidates? 13:57:26 q? 13:57:49 giuseppe: We could make another wiki page with the technologies and then list the requirements covered by them. 13:58:16 giuseppe: I can try to send an initial mail about the specs I was thinking of, and then after people have looked at it we can discuss it in the call. 13:58:48 -CyrilRa 13:58:50 ack kaz 13:59:36 kaz: In the MMI group we looked at a standard set of events to be used by several devices. These days, several vendors and hardware makers are joining the discussions. 14:00:08 kaz: We've started to think we need a separate resource manager. So I agree with you - we can generate a first round of ideas and then follow up in conference calls. 14:00:42 giuseppe: We can have a table with a column for each technology and put a cross for each one that is covered. 14:00:53 olivier: You can see this now in the Google spreadsheet. 14:01:21 olivier: It's in a new tab. 14:01:35 giuseppe: So each one of us should start looking at this. 14:01:53 Mark_Vickers has joined #webtv 14:02:18 olivier: Incidentally, requirements no. 24 does not have a link. 14:02:25 gmandyam: It's OK, I'll do that. 14:03:13 Bin_Hu: I suggest in column B, instead of listing the technologies one by one, we should call the column "technologies" and enter the individual technologies in the cells. 14:03:19 WFM 14:03:35 Bin_Hu: This should be easier to work with. 14:04:08 giuseppe: If you have more than one spec in a cell, you can't put status details in the cell in column C 14:04:31 olivier: How about three columns - tech 1, tech 2, tech 3. If there's more, we add a new column. 14:04:50 olivier: The idea is just to get an idea of how many technologies for each requirement. 14:05:02 +CyrilRa 14:05:09 olivier: I agree with both of you - crosses everywhere could be tedious. 14:05:32 giuseppe: It's probably better if people send an email to the list when they have technologies that cover a requirement. 14:05:43 giuseppe: It's not going to be hundreds anyway. 14:06:04 olivier: So, for homework, we should all send technology/requirement suggestions to the list. 14:06:10 CyrilRa has joined #Webtv 14:06:15 giuseppe: Yes, especially authors of the use cases. 14:06:31 olivier: Anything else to work on? 14:06:32 q+ 14:06:46 Topic: TPAC 14:06:46 olivier: One thing to think about is the face-to-face 14:07:12 -> http://www.w3.org/2013/11/TPAC/ TPAC page 14:07:20 olivier: If you haven't yet, please make your travel and especially hotel arrangements NOW! 14:07:32 olivier: If you need a visa, get an invitation letter for it NOW! 14:07:49 q+ to mention there is no room on Nov. 15th at Wuzhou Guest House (the main venue) 14:08:13 ack kaz 14:08:13 kaz, you wanted to mention there is no room on Nov. 15th at Wuzhou Guest House (the main venue) 14:08:19 olivier: There is a discussion on the mailing list about the agenda. Do we need to bring anything to the whole group in addition to our existing work? 14:08:49 kaz: Just to confirm, we should go head and make reservations for the hotel and start visa procedures as soon as possible. 14:08:49 ack gmandyam 14:09:20 gmandyam: Slight change of topic - some people on the call may know, the ATSC is working on version 3.0 of their tech. 14:09:22 ATSC has begun work on the ATSC 3.0 standard. Presentation layer and runtime requirements have been defined, and the group is examining HTML5 as a solution. Would it make sense to liase with the relevant subgroups in ATSC (e.g. written communication and/or joint meeting)? 14:09:29 Topic: ATSC 3.0 14:09:50 gmandyam: I can arrange a liaison if necessary. 14:10:00 glenn has joined #webtv 14:10:07 i/Slight change/topic: ATSC 3.0/ 14:10:12 s/Topic: ATSC 3.0// 14:10:19 rrsagent, draft minutes 14:10:19 I have made the request to generate http://www.w3.org/2013/10/02-webtv-minutes.html kaz 14:10:23 gmandyam: The group is not trying to re-invent the wheel. If both groups are doing similar gap analysis, it makes sense to avoid duplication. 14:10:39 gmandyam: Also, HbbTV is another tech that leverages HTML5 as well. 14:11:06 giuseppe: In terms of liaisons with other groups, we're very open to send and receive requests by individual groups. 14:11:12 giuseppe: No formal permission is needed. 14:11:33 giuseppe: Sometimes we have written to external groups, e.g. by the Testing TF, and got replies from various organisations. 14:11:50 giuseppe: Also, some external groups like HbbTV write to us with info. 14:12:14 gmandyam: There's a requirements doc in ATSC that's already been approved. 14:12:32 gmandyam: The official liaison letter would have a list of those requirements. 14:13:04 gmandyam: I imagine HbbTV is doing something similar. It would then be up to this IG to check through the list of requirements. 14:13:20 giuseppe: We could certainly use such as list with things we may not have considered. 14:13:27 s/as list/a list/ 14:13:51 ack gmandyam 14:13:56 giuseppe: About the agenda, we're not discussing that on the public list yet. 14:14:01 olivier: But will be in due course. 14:14:17 giuseppe: At TPAC, we should try to conclude this gap analysis. 14:14:31 giuseppe: We could maybe also discuss new use cases if there's time. 14:14:43 q? 14:14:46 +1 14:14:57 olivier: Any further business? 14:15:07 olivier: OK, we can adjourn. 14:15:18 CyrilRa has joined #Webtv 14:15:20 olivier: Next meeting is on 16th October, at the same time. 14:15:29 olivier: If you can't make it, please send your regrets. 14:15:38 Regrets oct 16 14:15:44 olivier: Call is adjourned. 14:15:45 -Mark_Vickers 14:15:46 -giuseppe 14:15:46 -Bin_Hu 14:15:47 -olivier 14:15:49 -gmandyam 14:15:51 -skim13,whyun 14:15:52 -ddavis 14:15:55 -Kazuyuki 14:15:56 thanks all 14:15:56 -CyrilRa 14:15:58 whyun has left #webtv 14:15:59 -igarashi 14:16:00 UW_WebTVIG()9:00AM has ended 14:16:00 Attendees were Kazuyuki, ddavis, giuseppe, +1.858.750.aaaa, gmandyam, +1.425.214.aabb, igarashi, +1.818.406.aacc, skim13, olivier, Mark_Vickers, CyrilRa, Bin_Hu, skim13,whyun 14:16:06 good meeting 14:16:07 [ adjourned ] 14:16:14 :) 14:16:18 Zakim, AAC is me 14:16:18 sorry, CyrilRa, I do not recognize a party named 'AAC' 14:16:20 chair: olivier 14:16:21 rrsagent, draft minutes 14:16:21 I have made the request to generate http://www.w3.org/2013/10/02-webtv-minutes.html kaz 14:16:25 Zakim, aacc is me 14:16:26 sorry, CyrilRa, I do not recognize a party named 'aacc' 14:16:44 rrsagent, stop