13:50:35 RRSAgent has joined #webtv 13:50:35 logging to http://www.w3.org/2011/07/26-webtv-irc 13:50:48 Meeting: Home Networking Task Force Telconf 13:58:10 zakim, call kazuyuki-617 13:58:10 ok, kaz; the call is being made 13:58:11 UW_WebTVIG(Home Net)10:00AM has now started 13:58:13 +Kazuyuki 13:58:23 zakim, who is here? 13:58:23 On the phone I see Kazuyuki 13:58:24 On IRC I see RRSAgent, Zakim, kaz, Clarke, MattH, trackbot 13:58:30 +??P6 13:58:41 zakim, ??P6 is MattH 13:58:41 +MattH; got it 13:58:56 +??P8 13:58:58 -??P8 13:59:04 + +1.703.234.aaaa 13:59:28 igarashi has joined #webtv 13:59:32 +??P8 13:59:38 zakim, aaaa is Jerry 13:59:38 +Jerry; got it 13:59:58 zaim, ??P8 is Clarke 14:00:28 aizu has joined #webtv 14:00:42 zakim, ??P8 is Clarke 14:00:42 +Clarke; got it 14:01:31 + +1.303.503.aabb 14:02:07 +??P18 14:02:17 zakim, aabb is Bob 14:02:17 +Bob; got it 14:02:20 donghyun_kang_ has joined #webtv 14:02:24 zakim, ??P18 is Igarashi 14:02:24 +Igarashi; got it 14:02:27 zakim, who is here? 14:02:27 On the phone I see Kazuyuki, MattH, Jerry, Clarke, Bob, Igarashi 14:02:28 On IRC I see donghyun_kang_, aizu, igarashi, RRSAgent, Zakim, kaz, Clarke, MattH, trackbot 14:03:40 Jerry has joined #webtv 14:03:47 +??P22 14:04:11 Zakim, ??P22 is me 14:04:11 +aizu; got it 14:04:22 agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2011Jul/0052.html 14:04:37 agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2011Jul/0051 14:04:42 + +1.503.712.aacc 14:05:15 zakim, aacc is Narm 14:05:15 +Narm; got it 14:05:28 topic: ISSUE-17 14:05:32 issue-17? 14:05:32 ISSUE-17 -- Use Case: Home Network Enabled User-Agent -- raised 14:05:32 http://www.w3.org/2011/webtv/track/issues/17 14:05:54 narmgadiraju has joined #webtv 14:06:08 kaz: let's close this 14:06:11 everyone: ok 14:06:16 close issue-17 14:06:17 ISSUE-17 Use Case: Home Network Enabled User-Agent closed 14:06:31 topic: ISSUE-24 14:06:33 issue-24? 14:06:33 ISSUE-24 -- Local Link of web applications -- raised 14:06:33 http://www.w3.org/2011/webtv/track/issues/24 14:06:35 rbardini has joined #webtv 14:06:57 + +82.26.91.2.aadd 14:07:23 zakim, aadd is DongHyun 14:07:23 +DongHyun; got it 14:07:38 + +1.408.356.aaee 14:07:52 -> http://lists.w3.org/Archives/Public/public-web-and-tv/2011Jul/0046.html Igarashi's update 14:08:02 igarashi: added description on API types 14:08:12 ... issue-24 itself is a generic API 14:09:07 -Bob 14:09:15 -> http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/LocalLink#Use_Case:_Local_Link_of_Web_Applications ISSUE-24 description 14:09:37 kaz: is the wiki description also updated? 14:09:40 igarashi: yes 14:10:42 +Bob 14:10:50 kaz: do you want to include the information on ISSUE-9 and Opera's API proposal 14:11:06 s/proposal/proposal in the wiki description as well?/ 14:11:27 igarashi: no, it's just additional explanation on what "generic API" means 14:11:48 kaz: any opinion? 14:12:05 ... if no objection, let's accept this proposal ISSUE-24 14:12:21 RESOLUTION: accept ISSUE-24 14:13:31 zakim, aaee is Richard 14:13:31 +Richard; got it 14:13:54 topic: MattH's proposals 14:14:15 matt: would like to start with 20 14:14:18 issue-20? 14:14:18 ISSUE-20 -- TV Querying and Control -- raised 14:14:18 http://www.w3.org/2011/webtv/track/issues/20 14:14:39 matt: restructured the issue 14:15:31 ... possible interaction scenario is included 14:15:44 ... JavaScript level API proposal for discussion as well 14:16:14 http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/TVControl 14:17:34 s/http/-> http/ 14:17:49 s/TVControl/TVControl Wiki description of ISSUE-20/ 14:18:02 matt: (describes the detail of the proposal) 14:19:17 q+ 14:19:17 jerry: trying to understan 14:19:22 s/understan/understand/ 14:19:35 ... target of the application which execute the API 14:19:44 ... how to know where to execute APIs? 14:20:00 ... home network devices could have a gateway 14:20:48 ... server needs to know where to get the content from 14:21:25 matt: the intention is implementing APIs as JavaScript and use from Web browsers 14:21:45 ... what content is available where is an issue 14:22:11 ... suppose DLNA terminology, media rendering device? 14:22:52 jerry: I think what you're saying is a TV device 14:22:57 matt: could be a TV device 14:23:06 ... or a desktop browser 14:24:12 jerry: target of the API is a processing engine that has capability of discovering 14:24:49 ... being discovered by the browser 14:25:00 ... and capable of executing the APIs 14:25:30 s/of discovering// 14:25:49 ... and that can describe what devices are/ 14:26:05 igarashi: in this scenario, application is rather a device 14:26:29 ... but application is running on devices 14:26:35 matt: will update the text 14:26:40 q? 14:27:31 igarashi: this service-specific API is supported by the TV as well? 14:27:56 matt: the API could be supported by TV if it can process JavaScript 14:28:00 ack c 14:28:11 clarke: your suggestion is higher level API 14:28:19 ... list of functions 14:28:21 ... right? 14:28:26 matt: yes 14:28:27 q- 14:28:47 igarashi: in scenario 1, there are several options 14:29:24 ... maybe you should not use sequence number, but should use non-ordered list 14:30:02 ... the first step "The application discovers..." should be done first, though 14:30:06 matt: will change 14:30:17 bob: a question 14:30:21 ... level of APIs 14:30:39 ... high-level APIs is useful 14:30:57 ... but what level of APIs should be used? 14:31:24 matt: there is ability for application 14:31:27 q+ 14:32:30 bob: we started a high-level APIs within AT&T, and would like to know how to cover the other implementations 14:32:54 ... need more sofisticated kind of APIs? 14:33:15 matt: if you have information to share with me, would be appreciated 14:33:55 bob: agree the trade-off 14:34:24 ... but how much task is expected for a User Agent? 14:34:39 q? 14:35:24 ... clarke's paper will be soon available 14:35:52 clarke: if we do something Bob suggested, i.e., lower-level APIs implementable 14:36:07 ... any preference from W3C viewpoint? 14:37:26 q- 14:37:30 kaz: both levels would be welcome and useful 14:37:53 ... our proposals should go to the other WGs, e.g., DeviceAPIs and WebApps 14:38:40 ... if they don't work very well for our proposals, we should create yet another WG :) 14:38:44 q? 14:39:13 action: hammonds to update issue-20 14:39:13 Sorry, couldn't find user - hammonds 14:39:21 action: matt to update issue-20 14:39:21 Created ACTION-56 - Update issue-20 [on Matt Hammond - due 2011-08-02]. 14:39:37 igarashi: comment on scenario 2 14:40:08 ... specific program? 14:40:24 matt: question on step 2 14:40:29 s/2/2?/ 14:40:33 igarashi: yes 14:40:47 matt: list of content available could be provided 14:41:07 ... and we could ask the TV which program is available now 14:41:21 igarashi: ok 14:41:40 -Bob 14:42:00 kaz: igarashi, do you want clarification in scenario 2? 14:42:30 igarashi: "application query" would be easier to understand? 14:42:36 matt: will use the term 14:43:09 http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/MediaIdentification 14:43:18 topic: ISSUE-19 14:43:21 issue-19? 14:43:21 ISSUE-19 -- Media Identification -- raised 14:43:21 http://www.w3.org/2011/webtv/track/issues/19 14:44:12 matt: content identifier 14:44:50 ... hopefully more clear 14:45:00 ... related to part of issue-20 14:45:15 q? 14:45:24 q? 14:45:26 q+ 14:46:27 kaz: do you think a specific URI could be used? 14:46:37 matt: a URI is a possibility 14:46:51 ... BBC would like to include URI style identifier 14:47:37 ... some provider might use different kind of identifier on some platform 14:48:00 kaz: can we accept this proposal? 14:48:11 everybody: no objections 14:48:23 RESOLUTION: ISSUE-19 is accepted 14:48:41 http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/TimeSynchronisation 14:48:56 topic: ISSUE-21 14:48:58 issue-21? 14:48:58 ISSUE-21 -- Time synchronisation -- raised 14:48:58 http://www.w3.org/2011/webtv/track/issues/21 14:49:14 matt: have no time to update this... 14:49:30 ... (explains the proposal) 14:50:08 ... similar to issue-19, any high-level APIs could be supported rather than application-specific APIs 14:50:45 kaz: you'll update the description, and we should talk about this next week? 14:50:49 matt: yes 14:51:21 kaz: no more proposals for today? 14:51:23 matt: no 14:51:41 -Richard 14:51:47 -Narm 14:51:49 -Clarke 14:51:56 kaz: any other topics? 14:51:56 -Jerry 14:51:57 -MattH 14:51:57 -aizu 14:52:01 everybody: no 14:52:03 -Igarashi 14:52:05 -DongHyun 14:52:18 kaz: ok. let's adjourn this call and talk with you all next week 14:52:36 ... Giuseppe will be also available next week 14:52:42 -Kazuyuki 14:52:43 [ adjourned ] 14:52:44 UW_WebTVIG(Home Net)10:00AM has ended 14:52:46 Attendees were Kazuyuki, MattH, +1.703.234.aaaa, Jerry, Clarke, +1.303.503.aabb, Bob, Igarashi, aizu, +1.503.712.aacc, Narm, +82.26.91.2.aadd, DongHyun, +1.408.356.aaee, Richard 14:53:23 Present: Kazuyuki, MattH, Jerry, Clarke, Igarashi, aizu, Narm, DongHyun, Richard, Bob 14:54:08 Chair: Kaz 14:54:12 Scribe: Kaz 14:54:28 rrsagent, make log public 14:54:33 rrsagent, draft minutes 14:54:33 I have made the request to generate http://www.w3.org/2011/07/26-webtv-minutes.html kaz 14:56:02 s/sofisticated/sophisticated/ 14:56:05 rrsagent, draft minutes 14:56:05 I have made the request to generate http://www.w3.org/2011/07/26-webtv-minutes.html kaz 14:57:47 Regrets: Giuseppe, Francois 14:57:50 rrsagent, draft minutes 14:57:50 I have made the request to generate http://www.w3.org/2011/07/26-webtv-minutes.html kaz 14:59:31 s/MattH's proposals/ISSUE-20/ 14:59:34 rrsagent, draft minutes 14:59:34 I have made the request to generate http://www.w3.org/2011/07/26-webtv-minutes.html kaz 15:15:45 MattH has left #webtv 17:03:36 Zakim has left #webtv