13:54:35 RRSAgent has joined #webtv 13:54:35 logging to http://www.w3.org/2011/08/16-webtv-irc 13:54:37 RRSAgent, make logs world 13:54:39 Zakim, this will be 13:54:39 I don't understand 'this will be', trackbot 13:54:40 Meeting: Web and TV Interest Group Teleconference 13:54:40 Date: 16 August 2011 13:55:02 zakim, what conferences? 13:55:02 I see UW_WebTVIG(Home Net)10:00AM, Team_(RevCadence)9:00AM, TAG_(AWWSW)9:00AM active 13:55:04 also scheduled at this time are MWI_BPWG()9:30AM, SW_(SPARQL)10:00AM, XML_(TAG TF)10:00AM, T&S_EGOV()9:00AM, Team_(PADIS)10:00AM, T&S_XMLSEC()10:00AM, WS_SOAP-JM()10:00AM, 13:55:07 ... Team_(MEET)10:00AM, Team_(iata)14:00Z, WAI_PFWG(HTML TF)9:00AM, VB_VBWG()10:00AM, IA_Team()10:00AM, WF_(ISOC)9:30AM 13:55:11 zakim, this will be UW_WebTVIG 13:55:12 ok, francois, I see UW_WebTVIG(Home Net)10:00AM already started 13:55:32 Meeting: Home Network Task Force Teleconference (Web and TV IG) 13:55:35 Chair: Giuseppe 13:55:46 Agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2011Aug/0093.html 13:55:52 zakim, who is on the line 13:55:52 I don't understand 'who is on the line', giuseppe 13:55:53 r_berkoff has joined #webtv 13:56:10 +Kazuyuki 13:56:15 zakim, who is here? 13:56:15 On the phone I see rberkoff, ??P7, Kazuyuki (muted) 13:56:17 On IRC I see r_berkoff, RRSAgent, Zakim, MattH, giuseppe, francois, kaz, trackbot 13:56:24 -Kazuyuki 13:56:32 zakim, ??P7 is me 13:56:32 +giuseppe; got it 13:56:35 zakim, who is here? 13:56:35 On the phone I see rberkoff, giuseppe 13:56:38 On IRC I see r_berkoff, RRSAgent, Zakim, MattH, giuseppe, francois, kaz, trackbot 13:56:45 JanL has joined #webtv 13:56:47 +Kazuyuki 13:56:59 +??P9 13:57:10 zakim, ??P9 is MattH 13:57:10 +MattH; got it 13:57:33 zakim, mute me 13:57:33 Kazuyuki should now be muted 13:57:34 +francois 13:57:38 zakim, who is noisy? 13:57:41 zakim, mute me 13:57:41 francois should now be muted 13:57:49 kaz, listening for 10 seconds I heard sound from the following: 5 (28%), giuseppe (38%), MattH (4%) 13:57:54 +??P12 13:58:01 zakim, unmute me 13:58:01 Clarke has joined #webtv 13:58:02 Kazuyuki should no longer be muted 13:58:38 +Cecile_Marc 13:58:40 dcorvoysier has joined #webtv 13:58:47 zakim, ??P12 is Clarke 13:58:52 +Clarke; got it 13:59:03 zakim, Cecile_Marc is really David_Corvoysier 13:59:10 +David_Corvoysier; got it 13:59:27 zakim, who is noisy? 13:59:47 francois, listening for 10 seconds I heard sound from the following: giuseppe (80%) 13:59:52 +JanL 13:59:59 zakim, mute giuseppe 14:00:05 zakim, unmute giuseppe 14:00:07 ack me 14:00:10 giuseppe should now be muted 14:00:14 giuseppe should no longer be muted 14:00:43 zakim, mute me 14:00:43 -giuseppe 14:00:44 francois should now be muted 14:01:32 +Tatsuya_Igarashi 14:01:42 + +1.303.503.aaaa 14:01:52 zakim, aaaa is Bob_Lund 14:01:52 +Bob_Lund; got it 14:02:00 ack me 14:02:02 + +46.1.34.79.aabb 14:02:09 zakim, mute me 14:02:09 francois should now be muted 14:02:17 zakim, aabb is Giuseppe 14:02:20 +Giuseppe; got it 14:02:20 zakim, +46 is me 14:02:21 sorry, giuseppe, I do not recognize a party named '+46' 14:02:26 -Bob_Lund 14:03:02 scribe: francois 14:03:09 Giuseppe: comment on the agenda? 14:03:30 Topic: Requirements document 14:03:43 http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Requirements 14:03:47 Giuseppe: I've done some work this week. Not completely done, but almost. 14:03:55 ... merging use cases and extracting requirements. 14:04:05 ... First of all, I'd like to summarize our plan for this document. 14:04:23 ... First, finalize this by the end of this month. 14:04:38 ... Then include the rest of the IG in the discussion to bring further comments. 14:04:47 +Bob_Lund 14:04:53 +Richard_Bardini 14:05:02 ... Then we'll bring this document to the IG F2F for final review, and then document ready can be published. 14:05:04 rbardini has joined #webtv 14:05:31 ... I tried to structure the document with a requirements section. 14:05:45 ... I tried to link the use cases with the requirements. 14:06:00 narm_gadiraju has joined #webtv 14:06:03 ... I'd like to ask everyone to go through the list of requirements and check associations. 14:06:13 ... Propose updates when you're concerned about something. 14:06:17 Present: rberkoff, Kazuyuki, MattH, francois, Clarke, David_Corvoysier, JanL, Tatsuya_Igarashi, Giuseppe, Bob_Lund, Richard_Bardini 14:06:30 -rberkoff 14:06:35 ... What is really important is the requirements, the use cases could perhaps be marked as informative. 14:06:52 +rberkoff 14:06:54 ... They are very important to understand the requirements, but maybe this section could be marked as informative. 14:07:13 ... Then there's a section on security. 14:07:22 ... I welcome any comment on the document. 14:07:48 ... The whole document needs to be approved in the end, even if we approved all use cases. Open issues need to be addressed if they exist. 14:08:04 +q 14:08:05 ... If disagreement, we'll add a section to highlight the lack of consensus within the group. 14:08:15 +q 14:08:31 Bob: Any idea how to indicate the priorities? 14:08:55 Giuseppe: good question. This needs to be reflected somehow in the document. I don't have a strong opinion. 14:09:16 ... One way could be to identify requirements by number and add a mapping table with 3 priority levels. 14:09:27 ... in a dedicated section. 14:10:11 narm is the one who spoke 14:10:13 q? 14:10:24 s/Bob:/Narm:/ 14:11:05 Matt: Thanks, great job. I had a little look earlier. Looking at requirements Application communication. We might clarify that it is for direct communication and not for communication through intermediaries. 14:11:26 Giuseppe: OK, I'd like to suggest you bring this comment to the mailing-list so that others can comment. 14:11:33 Matt: Sure. 14:11:39 q+ 14:11:41 ack MattH 14:11:53 q+ 14:11:59 Giuseppe: About use cases, people will have to check mapping to requirements. 14:12:01 q? 14:12:04 ack JanL 14:12:35 Jan: the doc includes links to the original issue and use cases. 14:13:06 ... and copies the text to the original issue. 14:13:40 ... Do you want us to update the initial text or do you plan to remove this "Original Proposal" link afterwards? 14:13:50 Giuseppe: I plan to remove the links afterwards. 14:14:20 ... Email discussions should be good to update text in use cases. 14:14:28 q? 14:14:31 ack francois 14:17:59 francois: @@@on requirements that would better be addressed at "conforming specifications" 14:18:03 zakim, mute me 14:18:03 francois should now be muted 14:18:19 Giuseppe: Got it, ok with the approach? 14:18:45 Kaz: yes, useful to add, could perhaps be done in the working group that takes the requirements spec. 14:19:08 ... Also mention the working group that is likely to take on the work. 14:19:20 ... Francois comment is good but too advanced, I think. 14:19:34 ... We don't really need that clarification for this requirements document. 14:19:51 Giuseppe: It's an easy change to do, and I'm fine with it. 14:19:57 ack k 14:19:58 ... Any other comment? 14:20:05 [none heard] 14:20:23 Topic: Propose text to expand ISSUE-26 and ISSUE-28 to address Jan's comment (ACTION-69) 14:20:27 ACTION-69? 14:20:27 ACTION-69 -- Russell Berkoff to propose text to expand ISSUE-26 and ISSUE-28 to address Jan's comment -- due 2011-08-16 -- OPEN 14:20:27 http://www.w3.org/2011/webtv/track/actions/69 14:20:37 Jan: it looks perfect. Very good addition. 14:20:50 ... Question is what do I do with the initial text? 14:21:13 Giuseppe: I'll deal with it. So we can close the issues and I'll merge the text Russell proposed in the Requirements document. 14:21:45 ACTION: Giuseppe to update text of ISSUE-26 and ISSUE-28 based with text proposed by Russell in ACTION-69 14:21:46 Created ACTION-71 - Update text of ISSUE-26 and ISSUE-28 based with text proposed by Russell in ACTION-69 [on Giuseppe Pascale - due 2011-08-23]. 14:21:51 close ACTION-69 14:21:51 ACTION-69 Propose text to expand ISSUE-26 and ISSUE-28 to address Jan's comment closed 14:21:58 close ISSUE-26 14:21:58 ISSUE-26 Home Network Enabled User Agent - Network Media Player closed 14:22:01 close ISSUE-28 14:22:01 ISSUE-28 Home Network Enabled User-Agent - Network Media Controller closed 14:22:17 Topic: See if ISSUE-14 and ISSUE-30 can be merged (ACTION-66) 14:22:28 action-66? 14:22:28 ACTION-66 -- Russell Berkoff to see if ISSUE-14 and ISSUE-30 can be merged -- due 2011-08-09 -- OPEN 14:22:28 http://www.w3.org/2011/webtv/track/actions/66 14:22:51 Russell: ISSUE-14 is on services not necessarily connected to a target in my view. 14:23:24 ... whereas ISSUE-30 is really about support of devices and then services as a means to change the state of the device. 14:23:33 ... I tried to give examples of differences in my email. 14:24:31 Giuseppe: My impression from the description of ISSUE-14 is that it's not particularly either stateless or stateful, so I would think your use case is included here. 14:24:54 Russell: ISSUE-14 does not have a strong notion of discovering a device, rather a notion of discovering a service. 14:25:12 ... whereas ISSUE-30 is more bound to a device, and then discovery of services on that device. 14:25:45 Giuseppe: I would be fine to keep ISSUE-30 in as a way to clarify what use cases we're trying to cover, even though I think it's pretty generic. 14:26:00 ... It will probably generate the same requirements though. 14:26:11 q+ 14:26:46 Bob: I agree with you Giuseppe. The distinction between discovering devices and discovering services on devices would generate the same requirements. 14:26:48 q- 14:27:53 Giuseppe: I would like to improve the use case that is in. Could you perhaps suggest a better wording of use case 1? 14:28:05 ... Wait, I was not looking at the right issue. 14:28:28 ... I believe the action was mis-recorded, it's ISSUE-4, not ISSUE-14. 14:28:41 ... So U1 in the requirements document. 14:28:55 ... We can probably extend the use case a little bit, could you look into it? 14:29:02 Russell: OK, I'll have a look. 14:29:12 -Bob_Lund 14:29:27 +??P25 14:29:40 q? 14:29:42 Giuseppe: Conclusion is to look at U1 for ISSUE-4 and propose text if it's not enough. 14:29:57 zakim, ??P25 is Bob 14:29:57 +Bob; got it 14:29:58 zakim, ??P25 is Bob_Lund 14:29:59 I already had ??P25 as Bob, francois 14:30:24 Giuseppe: We'll close action and issue next week. 14:30:52 Topic: Comments on Home Network Enabled User-Agent use cases 14:31:04 zakim, who is noisy? 14:31:14 francois, listening for 10 seconds I heard sound from the following: Bob (56%) 14:31:18 Topic: Missing HNTF Deliverables 14:31:37 http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Charter#Deliverables 14:32:05 Giuseppe: One is gap. That's covered with use cases and requirements document. 14:32:23 ... Another item is to categorize all the use cases/requirements. 14:32:40 ... I'd be happy to hear your opinions on this. 14:33:03 ... If they are equally important, we can skip this categorisation phase. 14:33:50 ... Looking at the different options we have in the charter. [going through the list]. 14:34:20 q+ 14:34:36 ... I need input from the group here. 14:34:54 q? 14:34:55 ... i.e. shoot for option 6, with liaisons to some groups perhaps. 14:35:39 -Tatsuya_Igarashi 14:35:45 Matt: We already know that DAP is to take device discovery. [lots of echo]. I would suggest that's a main chunk of what we're trying to achieve, so moving to there sounds good. 14:36:15 Giuseppe: Right, that's exactly the kind of input I'm looking for, so we can propose recommendations to W3C Director. 14:36:23 q+ 14:36:58 q- 14:37:14 Giuseppe: It seems a good idea to start with the DAP group since it's already listed in the new charter, and then check from there what needs to be defined on top of that later on. 14:37:33 ack me 14:37:43 q? 14:38:27 Bob: In order for the result of the work to be consistent, it may make sense to put all our requirements into one working group. 14:38:39 Giuseppe: I'm not sure if it's the best thing to do. 14:39:08 ... If requirements on Media Pipeline TF impact on the video, perhaps the HTML WG is better for that. 14:39:28 ... But some of our requirements, we may suggest to have another WG handle them. 14:39:52 Bob: How do you maintain consistency if work is carried on in different groups? 14:39:55 q+ 14:40:02 ack Clarke 14:40:03 ack francois 14:40:12 That was Clarke talking, not Bob 14:40:29 s/Bob: In/Clarke: In/ 14:40:35 thanks 14:40:39 s/Bob: How/Clarke: How/ 14:41:18 q+ 14:41:32 Francois: @@W3C Process is meant to address this. 14:43:08 Giuseppe: yes, and too many deliverables or too broad a scope may hamper the progress of a group. 14:43:38 ... for the Media Pipeline TF, it seems more focused on extensions to the video tag, so HTML WG sounds the right place for discussions. 14:43:57 Francois: yes, but not necessarily, it could be done in a separate WG. 14:44:08 [scribe missed last exchange] 14:44:45 My point was that if anyone is concerned about alignment between working groups they should participate in both working groups. 14:45:04 Giuseppe: On the WG part, I would propose to give the document as it is to DAP, as it seems to be matching their charter. 14:45:16 ack me 14:46:05 q? 14:46:16 ... When it comes to categorize use cases/requirements, I would say it falls in the category "new requirements for a WG", so basically we're good. 14:46:25 ... That's my proposal. 14:46:40 ... Feel free to comment. The priority discussion is still open. 14:46:49 q+ bob 14:46:53 ack b 14:47:17 Bob: I have a suggestion on priorities. Set of requirements that represent the minimal amount of work you'd need to do to enable scenarios. 14:47:44 ... That would create a mandatory set of requirements, and a "larger" set of requirements, leading to an easy distinction. 14:47:53 Giuseppe: yes, sounds like a good approach. 14:47:56 zakim, mute me 14:47:56 francois should now be muted 14:48:32 Giuseppe: Some of the requirements may require more investigation, such as migration scenarios for instance, others may be easier to do. I'm fine with your distinction. 14:48:55 q+ 14:49:24 Clarke: we could ask someone to volunteer to take a first stab. 14:49:25 q- 14:49:43 ... s/someone/a few people/ 14:50:00 Clarke: to have something to start from and see if adjustment is needed. 14:50:24 q+ 14:50:26 Giuseppe: Yes, I'd like to ask people here to categorize the requirements, so we can review that next week. 14:50:30 zakim, unmute me 14:50:30 Kazuyuki should no longer be muted 14:50:34 ... Fine with everybody? 14:50:41 [nodding "heard"] 14:51:00 Kaz: Question about relationship with RFC2119. 14:51:11 ... First priority is MUST statements, right? 14:51:32 Giuseppe: I was more thinking about a time schedule rather than MUST/SHOULD. 14:51:48 ack k 14:52:23 ... We need base functionality to enable basic home networking scenarios, then more to build on top of it. 14:52:51 Kaz: Yes, it could be done later, fine to proceed with priority in the TF. 14:53:17 Giuseppe: I think these are two different things, actually, so I would proceed with priorities even in the final report. 14:54:11 http://lists.w3.org/Archives/Public/public-web-and-tv/2011Aug/0085.html 14:54:12 ... Please send me (or to the mailing-list) a list of which requirements should be in which category, and I'll make a summary next week for discussion. 14:54:33 Topic: Comment on Home Network Enabled User-Agent use cases 14:55:54 [Giuseppe and Russell about status of email exchanges] 14:56:30 "Provide a mean for applications to control some of the parameters that may be needed to be expose to support well-established home network protocols. A more detailed analysis is needed to identify such parameters and a way to specify them in a transport agnostic way" 14:57:57 Giuseppe: we need to identify requirements, we cannot be too vague. My suggestion would be to look at precise requirements so that a WG can action these requirements. 14:58:36 ... We could phrase as "we've identified a gap here on transport headers, and the WG should look into these" 14:58:50 Russell: It's a fairly broad topic, so simple requirements might help. 14:59:44 Giuseppe: It wasn't clear to me what the sentence covered. 15:00:01 Russell: It used to say DLNA, but there was a request to remove mentions of DLNA. 15:00:10 Giuseppe: but the use case is not about DLNA. 15:00:20 ... I'm not suggesting to change the meaning, merely to clarify the requirement. 15:01:03 Russell: The point of the response was that the headers provide info for the user-agent, the application and playback engine. 15:01:13 q+ 15:01:37 -Richard_Bardini 15:02:12 Giuseppe: Again, I'm not suggesting to change the meaning, but to clarify and point the WG to that saying it needs to be addressed. 15:02:23 ... Probably easier if you reply on the actual text. 15:02:24 q- 15:02:34 ... Same for the other two points. 15:02:44 ... Let's conclude on the mailing-list. 15:03:11 Russell: How do people in the TF feel about compatibility forward or backward? 15:03:25 Clarke: Could you provide examples? 15:03:46 Russell: Dealing with older user-agents, for instance. 15:04:14 Clarke: sounds like a core architectural design point. 15:04:29 I think that was Jan, not Clarke 15:04:37 Giuseppe: I don't think it's part of a spec, more a point for the community to check how they can support the feature in old browsers. 15:04:46 s/Clarke: Could/Jan: Could/ 15:04:53 s/Clarke: sound/Jan: sound/ 15:05:14 Russell: If people feel this way, ok to dropping. 15:05:18 -Bob 15:05:28 [scribe missed precise comments because of echo] 15:05:43 -Clarke 15:05:43 Giuseppe: ok, running out of time, closing call now. Have a good day! 15:05:44 -JanL 15:05:45 -Giuseppe 15:05:45 -MattH 15:05:46 -rberkoff 15:05:47 -francois 15:05:50 [Call adjourned] 15:05:50 [ btw, some clarification for Clarke's concern: 1. we should not invent "wheels" again, 2. we have Hypertext Coordination Group formed by WG/IG Chairs for inter-group coordination, 3 if needed we could consider some meta mechanism like SMIL, RDF and MMI to integrate several specifications consistently ] 15:05:59 -Kazuyuki 15:06:04 quit 15:06:11 MattH has left #webtv 15:06:37 I have made the request to generate http://www.w3.org/2011/08/16-webtv-minutes.html kaz 15:11:00 disconnecting the lone participant, David_Corvoysier, in UW_WebTVIG(Home Net)10:00AM 15:11:02 UW_WebTVIG(Home Net)10:00AM has ended 15:11:06 Attendees were rberkoff, Kazuyuki, giuseppe, MattH, francois, Clarke, David_Corvoysier, JanL, Tatsuya_Igarashi, +1.303.503.aaaa, Bob_Lund, +46.1.34.79.aabb, Richard_Bardini, Bob 15:11:32 RRSAgent, draft minutes 15:11:32 I have made the request to generate http://www.w3.org/2011/08/16-webtv-minutes.html francois 15:15:09 giuseppe has left #webtv 15:48:22 Panu has joined #webtv 16:05:35 panze has joined #webtv 16:06:28 panze has left #webtv 17:16:31 Zakim has left #webtv