IRC log of webtv on 2011-08-02

Timestamps are in UTC.

13:55:34 [RRSAgent]: RRSAgent has joined #webtv
13:55:34 [RRSAgent]: logging to http://www.w3.org/2011/08/02-webtv-irc
13:55:36 [trackbot]: RRSAgent, make logs world
13:55:38 [trackbot]: Zakim, this will be
13:55:38 [Zakim]: I don't understand 'this will be', trackbot
13:55:39 [trackbot]: Meeting: Web and TV Interest Group Teleconference
13:55:39 [trackbot]: Date: 02 August 2011
13:55:56 [francois]: Meeting: Home Networking Task Force Teleconference
13:56:04 [francois]: s/Meeting: Web and TV Interest Group Teleconference/
13:56:09 [francois]: Chair: Giuseppe
13:56:28 [RRSAgent]: I have made the request to generate http://www.w3.org/2011/08/02-webtv-minutes.html kaz
13:56:29 [Zakim]: UW_WebTVIG(Home Net)10:00AM has now started
13:56:35 [francois]: Agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2011Aug/0010.html
13:56:36 [Zakim]: +??P6
13:56:43 [kaz]: zakim, call kazuyuki-617
13:56:43 [Zakim]: ok, kaz; the call is being made
13:56:45 [Zakim]: +Kazuyuki
13:57:46 [Zakim]: +Bjorn_Bringert
13:57:49 [giuseppe]: zakim, +??P6 is giuseppe
13:57:49 [Zakim]: sorry, giuseppe, I do not recognize a party named '+??P6'
13:58:07 [Zakim]: +??P9
13:58:17 [kaz]: zakim, ??P9 is Matt
13:58:17 [Zakim]: +Matt; got it
13:58:24 [giuseppe]: zakim, ??P6 is giuseppe
13:58:24 [Zakim]: +giuseppe; got it
13:58:30 [kaz]: zakim, who is here?
13:58:30 [Zakim]: On the phone I see giuseppe, Kazuyuki, Bjorn_Bringert, Matt
13:58:31 [Zakim]: On IRC I see RRSAgent, MattH, rberkoff, giuseppe, Zakim, kaz, francois, trackbot
13:58:36 [MattH]: zakim, ??P9 is MattH
13:58:36 [Zakim]: I already had ??P9 as Matt, MattH
13:58:42 [kaz]: zakim, Bjorn_Bringert is Russell_Berkoff
13:58:42 [Zakim]: +Russell_Berkoff; got it
13:59:14 [MattH]: zakim, Matt is MattH
13:59:14 [Zakim]: +MattH; got it
14:00:03 [Zakim]: +francois
14:00:06 [francois]: zakim, mute me
14:00:07 [Zakim]: francois should now be muted
14:00:14 [francois]: ack me
14:00:57 [aizu]: aizu has joined #webtv
14:02:02 [igarashi]: igarashi has joined #webtv
14:02:14 [francois]: zakim, mute me
14:02:16 [Zakim]: + +1.215.286.aaaa
14:02:18 [Zakim]: francois should now be muted
14:02:45 [kaz]: zakim, aaaa is David_Mays
14:02:45 [Zakim]: +David_Mays; got it
14:02:47 [giuseppe]: http://www.w3.org/2011/webtv/track/products/2
14:02:47 [davidmays]: davidmays has joined #webtv
14:03:06 [davidmays]: zakim, who is here
14:03:06 [Zakim]: davidmays, you need to end that query with '?'
14:03:11 [davidmays]: zakim, who is here?
14:03:13 [Zakim]: On the phone I see giuseppe, Kazuyuki, Russell_Berkoff, MattH, francois (muted), David_Mays
14:03:15 [Zakim]: On IRC I see davidmays, igarashi, aizu, RRSAgent, MattH, rberkoff, giuseppe, Zakim, kaz, francois, trackbot
14:03:33 [giuseppe]: ISSUE-20?
14:03:33 [trackbot]: ISSUE-20 -- TV Querying and Control -- open
14:03:33 [trackbot]: http://www.w3.org/2011/webtv/track/issues/20
14:03:39 [MattH]: http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/TVControl
14:03:44 [francois]: scribe: francois:
14:03:56 [francois]: scribe: francois
14:03:58 [francois]: Topic: TV Querying and Control
14:04:12 [francois]: matt: re-write proposal to better explain what could be standardized.
14:04:24 [Zakim]: +??P46
14:04:32 [kaz]: zakim, ??P46
14:04:37 [aizu]: Zakim, ??P46 is me
14:04:38 [Zakim]: I don't understand '??P46', kaz
14:04:40 [kaz]: zakim, ??P46 is aizu
14:04:44 [francois]: ... The processing engine could be incorporated or not.
14:04:46 [Zakim]: +aizu; got it
14:04:50 [Zakim]: I already had ??P46 as aizu, kaz
14:05:00 [francois]: ... There were some questions I hope I've addressed.
14:05:02 [Zakim]: -Russell_Berkoff
14:05:05 [Zakim]: +??P44
14:05:13 [francois]: giuseppe: comments on this?
14:05:35 [kaz]: zakim, ??P44 is Clarke_Stevens
14:05:35 [Zakim]: +Clarke_Stevens; got it
14:05:52 [Zakim]: +??P7
14:05:56 [francois]: s/scribe: francois://
14:06:05 [Zakim]: +Russell_Berkoff
14:06:18 [kaz]: zakim, who is here?
14:06:18 [Zakim]: On the phone I see giuseppe, Kazuyuki, MattH, francois (muted), David_Mays, aizu, Clarke_Stevens, ??P7, Russell_Berkoff
14:06:19 [Zakim]: On IRC I see davidmays, igarashi, aizu, RRSAgent, MattH, rberkoff, giuseppe, Zakim, kaz, francois, trackbot
14:06:38 [francois]: giuseppe: I don't have specific comments. I see different challenges. One thing I noticed is that it does not follow the same approach as other things we've discussed.
14:06:44 [francois]: ... Not a generic approach.
14:07:31 [kaz]: zakim, ??P7 is igarashi
14:07:31 [Zakim]: +igarashi; got it
14:07:47 [francois]: ... On the use case, no problem it's fine.
14:07:56 [francois]: ... Any other comment, or can we conclude it's approved?
14:08:00 [mav]: mav has joined #webtv
14:08:08 [francois]: proposed RESOLUTION: approve ISSUE-20
14:08:19 [francois]: RESOLUTION: approve ISSUE-20, TV Querying and Control
14:08:27 [MattH]: http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/TimeSynchronisation
14:08:28 [francois]: ACTION: giuseppe to integrate ISSUE-20 in requirements spec
14:08:29 [trackbot]: Created ACTION-58 - Integrate ISSUE-20 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:08:43 [francois]: Topic: Time Synchronization (ISSUE-21)
14:08:51 [Zakim]: + +1.650.483.aabb
14:08:59 [francois]: matt: Same here, re-wrote to better explain what's up for standardization.
14:09:06 [kaz]: zakim, aabb is mav
14:09:06 [Zakim]: +mav; got it
14:09:47 [francois]: ... Regarding the time sync use case, the idea is to make it possible to be able to sync the content of their own app with the content played on the TV set.
14:10:04 [francois]: ... I believe we briefly described the prototype during the Berlin Workshop.
14:10:25 [kaz]: present: giuseppe, Kazuyuki, MattH, francois, David_Mays, aizu, Clarke_Stevens, igarashi, Russell_Berkoff, mav
14:10:29 [francois]: ... Re-focusing is to highlight the fact that it's useful for an app to have a simple and clear API to access this type of information.
14:10:34 [RRSAgent]: I have made the request to generate http://www.w3.org/2011/08/02-webtv-minutes.html kaz
14:11:18 [francois]: ... It would be useful to have a high-level API that can enable these kind of applications and that abstract away the possible inconsistencies.
14:12:02 [francois]: Russell: I object, the existing discovery protocol address these issues, so I believe it's out of scope.
14:12:37 [francois]: matt: I was referring to the previous situation. In the new version, I refer to existing protocols that can be appropriate, so you're right.
14:12:44 [francois]: Russell: ok.
14:12:53 [francois]: giuseppe: comments on the content of the issue?
14:13:05 [francois]: ... then we can approve this as well
14:13:27 [francois]: RESOLUTION: Approve ISSUE-21, Time synchronization
14:13:38 [francois]: ACTION: giuseppe to integrate ISSUE-21 in requirements spec
14:13:38 [trackbot]: Created ACTION-59 - Integrate ISSUE-21 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:14:14 [MattH]: http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/LipSyncTimeSynchronisation
14:14:22 [francois]: giuseppe: for some of these use cases, there could be an entity on the network that provides the service, so not necessarily a local API
14:14:24 [giuseppe]: ISSUE-22?
14:14:24 [trackbot]: ISSUE-22 -- Lip-sync Accuracy Time Synchronisation -- open
14:14:24 [trackbot]: http://www.w3.org/2011/webtv/track/issues/22
14:14:43 [francois]: Topic: Lip-Sync Accuracy Time Synchronisation (ISSUE-22)
14:15:05 [francois]: matt: related but with emphasis on needs for precise timing information, e.g. lip sync.
14:15:38 [francois]: ... The description here makes explicit the need to expose the accuracy that is available so that an app can determine whether it can do its stuff.
14:15:58 [francois]: giuseppe: thanks, any comment on this?
14:16:24 [kaz]: q?
14:16:32 [kaz]: q+
14:16:41 [francois]: ... OK, let's close this as well
14:16:44 [francois]: ack kaz
14:17:15 [Clarke]: Clarke has joined #webtv
14:17:21 [francois]: kaz: Matt, are you interested in not only lip-sync but also 3D, or animation, audio frame, or other multiple modalities?
14:17:56 [francois]: matt: I think these should be valid. We were more interested in audio at BBC, but I can see other purpose requiring accurate timing sync for other modality, yes.
14:18:11 [francois]: RESOLUTION: Approve ISSUE-22, Lip-sync Accuracy Time Synchronisation
14:18:28 [francois]: ACTION: Giuseppe to integrate ISSUE-22 in requirements spec.
14:18:28 [trackbot]: Created ACTION-60 - Integrate ISSUE-22 in requirements spec. [on Giuseppe Pascale - due 2011-08-09].
14:19:01 [francois]: Topic: UPnP/DLNA ecosystem support
14:19:01 [giuseppe]: ISSUE-23?
14:19:01 [trackbot]: ISSUE-23 -- UPnP/DLNA ecosystem support -- open
14:19:01 [trackbot]: http://www.w3.org/2011/webtv/track/issues/23
14:19:27 [francois]: Russell: Issue-23 is a use case to support the UPnP/DLNA ecosystem devices as-is within an application.
14:20:13 [francois]: ... There are a large number of currently deployed UPnP/DLNA devices, and having W3C user agents be able to support those devices would be beneficial for both orgs as well as for users.
14:20:54 [francois]: giuseppe: you didn't write any use case, right?
14:21:01 [francois]: russell: right.
14:21:15 [francois]: ... It's just to generate a requirement.
14:21:41 [giuseppe]: q?
14:21:52 [francois]: ... There are specific use cases which are written later on, but this is a specific use case to require UPnP/DLNA support.
14:22:11 [francois]: Giuseppe: no comment. Any comment?
14:22:48 [francois]: Russell: I think there should be a requirement that maps to this issue.
14:22:53 [kaz]: q+ to ask what rberkoff means by "W3C User -Agents" (maybe HTML-based Web browsers?)
14:23:06 [francois]: Giuseppe: OK, I can find a way to integrate that in requirements spec.
14:23:12 [giuseppe]: q?
14:23:35 [francois]: RESOLUTION: Approve ISSUE-23, UPnP/DLNA ecosystem support
14:23:48 [francois]: ACTION: giuseppe to integrate ISSUE-23 in requirements spec.
14:23:48 [trackbot]: Created ACTION-61 - Integrate ISSUE-23 in requirements spec. [on Giuseppe Pascale - due 2011-08-09].
14:25:19 [francois]: Russell: question is whether it's enough to support various protocols, or whether we need to dig up in types of services exposed and expose e.g. media servers.
14:26:16 [francois]: ... [Going through requirements]. Requirement to list content that matches precise criteria on a media server for instance. Playback operation.
14:26:47 [giuseppe]: q?
14:26:47 [francois]: ... View EPG data which may represent current content, also tune and play live content, and then select and play recorded content.
14:27:21 [francois]: i/Russell:/Topic: Home Network Enabled User-Agent - Network Media Player (ISSUE-26)
14:27:38 [francois]: kaz: my comment was on ISSUE-23. Clarify what you mean by W3C user agents?
14:27:58 [francois]: Russell: there are conceivably user agents that may not be browsers but something else.
14:28:19 [francois]: kaz: In that case, W3C specification compliant user agents. W3C does not produce user agents
14:28:24 [francois]: Russell: yes.
14:28:44 [francois]: Giuseppe: back to ISSUE-26, any comment?
14:29:01 [francois]: ... I don't think the use case is controversial.
14:29:11 [francois]: ... No problem with the use case itself.
14:29:35 [francois]: ... One problem I have with these use cases is that they all look different.
14:29:45 [francois]: ... We might want to re-write them for more consistency.
14:29:56 [francois]: Russell: I'm certainly willing to help.
14:30:13 [francois]: ... I tried to make the use cases and requirements consistent.
14:30:17 [francois]: Giuseppe: ok.
14:30:50 [francois]: RESOLUTION: Approve ISSUE-26, Home Network Enabled User-Agent - Network Media Player
14:31:03 [francois]: ACTION: Giuseppe to integrate ISSUE-26 in requirements spec
14:31:03 [trackbot]: Created ACTION-62 - Integrate ISSUE-26 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:31:32 [francois]: Topic: Home Network Enabled User-Agent - Network Media Server (ISSUE-27)
14:31:46 [francois]: Russell: companion use case to previous one, to be able to serve content.
14:31:57 [francois]: ... Media server not necessarily local, could be in the cloud.
14:32:27 [francois]: Giuseppe: there's a specific reference to DLNA in things to standardize.
14:33:05 [francois]: Russell: I was just trying to clarify what the term Home Network Media Transport Requirements might entail.
14:33:22 [francois]: ... May I just change "mainly" into "possibly"?
14:33:34 [francois]: ... It was really just meant as a clarification.
14:33:42 [francois]: ... I'll go through the use case and take that out.
14:33:46 [francois]: Giuseppe: ok, fine.
14:34:30 [francois]: RESOLUTION: Approve ISSUE-27, Home Network Enabled User-Agent - Network Media Server
14:34:37 [francois]: ACTION: Giuseppe to integrate ISSUE-27 in requirements spec
14:34:37 [trackbot]: Created ACTION-63 - Integrate ISSUE-27 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:34:40 [giuseppe]: q?
14:34:48 [kaz]: q-
14:34:58 [francois]: Topic: Home Network Enabled User-Agent - Network Media Controller (ISSUE-28)
14:35:18 [francois]: Russell: provides more details about what needs to be controlled on media that provides rendering.
14:35:41 [francois]: ... including closed captioning, camera angles, etc.
14:36:01 [francois]: Giuseppe: same as for ISSUE-27, DLNA mention remains.
14:36:12 [giuseppe]: q?
14:36:18 [francois]: Russell: Yes, I'll go through all of these issues and adjust the wording.
14:36:38 [francois]: Giuseppe: ok, also approved, then.
14:36:48 [francois]: RESOLUTION: Approve ISSUE-28, Home Network Enabled User-Agent - Network Media Controller
14:36:52 [francois]: ACTION: Giuseppe to integrate ISSUE-28 in requirements spec
14:36:52 [trackbot]: Created ACTION-64 - Integrate ISSUE-28 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:37:12 [francois]: Topic: Home Network Enabled User-Agent - Network Record Controller (ISSUE-29)
14:37:47 [francois]: Russell: different scenarios on controlling recorder, listed on the page.
14:37:55 [francois]: Giuseppe: Comments?
14:37:59 [francois]: ... Approved.
14:38:12 [francois]: RESOLUTION: Approve ISSUE-29, Home Network Enabled User-Agent - Network Record Controller
14:38:16 [francois]: ACTION: Giuseppe to integrate ISSUE-29 in requirements spec
14:38:16 [trackbot]: Created ACTION-65 - Integrate ISSUE-29 in requirements spec [on Giuseppe Pascale - due 2011-08-09].
14:38:32 [francois]: Topic: Home Network Enabled User-Agent - Network Device Controller (ISSUE-30)
14:39:20 [francois]: Russell: Control of a device, which we don't know anything about. There might be provisioning, e.g. home network management services while upgrading firmware. There's a whole slew of device types on top of media related services.
14:39:29 [francois]: ... This is a use case to control all sorts of devices.
14:39:55 [francois]: Giuseppe: given that this is generic, and that we already have approved generic use cases, does that add something?
14:40:19 [francois]: Russell: we do have Igarashi-san application use cases. But this is more control of non media devices on the home network.
14:40:27 [francois]: ... Usage will become increasibly important.
14:41:06 [francois]: Giuseppe: Yes, but requirements already covered by other issue, I think.
14:41:24 [francois]: ... High-level versus low-level.
14:41:35 [francois]: ISSUE-14?
14:41:35 [trackbot]: ISSUE-14 -- Document Discovering a Service -- closed
14:41:35 [trackbot]: http://www.w3.org/2011/webtv/track/issues/14
14:41:48 [giuseppe]: http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Requirements#U7._Application_Discovering_a_Service
14:41:55 [francois]: Giuseppe: The requirements doc is already updated to cover this.
14:42:19 [francois]: Russell: I might suggest that this gets merged with issue-14, provided there are no new requirements.
14:42:47 [francois]: ... One question that I have in mind. Is a device or service in these use cases the same as the device in the use case I'm providing?
14:43:25 [francois]: ... I think Jean-Claude mentioned the definition of a device as a list of services.
14:44:00 [francois]: ... I'm a little concerned about the definition section in the requirements doc.
14:44:06 [francois]: Giuseppe: it's for the scope of the document.
14:44:20 [francois]: Russell: I think we'll have to discuss devices vs. services
14:44:58 [francois]: Giuseppe: could you provide text for the requirements document?
14:45:00 [francois]: ack me
14:45:26 [francois]: ACTION: Russell to see if ISSUE-14 and ISSUE-30 can be merged
14:45:26 [trackbot]: Created ACTION-66 - See if ISSUE-14 and ISSUE-30 can be merged [on Russell Berkoff - due 2011-08-09].
14:45:35 [francois]: zakim, mute me
14:45:35 [Zakim]: francois should now be muted
14:46:19 [francois]: Topic: Next steps
14:46:30 [francois]: giuseppe: it would be nice to finish the document by the end of the month.
14:46:55 [francois]: ... I'll update it so that we can review it next time and approve it.
14:47:47 [francois]: ... The idea would be to publish the requirements document, and then to add some section in the IG report about our findings.
14:48:42 [francois]: ... What should we do with CableLabs draft proposal?
14:49:09 [francois]: ... We need to know what we're going to do with other documents such as implementation alternatives.
14:49:30 [francois]: Clarke: hard to understand you right now, let's do a phone call and come up with a plan or something.
14:50:15 [francois]: Topic: CableLabs Simplified Home Networking API Proposal
14:50:30 [francois]: Giuseppe: question, Clarke, is what should the group do with this?
14:50:43 [francois]: Clarke: I'd like people to comment on it, see if it meets requirements.
14:50:48 [kaz]: -> http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/RevisedAPI Wiki
14:50:51 [kaz]: issue-38?
14:50:51 [trackbot]: ISSUE-38 -- CableLabs Simplified Home Networking API Proposal -- open
14:50:51 [trackbot]: http://www.w3.org/2011/webtv/track/issues/38
14:50:59 [francois]: ... Then look at this proposal and the one from Opera, see if they can be aligned.
14:51:11 [kaz]: s/... Then/Clarke: Then/
14:51:17 [francois]: ... I'm working on an update to that document, which I can publish in the next couple of days.
14:51:47 [francois]: Giuseppe: [chunked], include in the report?
14:52:17 [francois]: Clarke: yes, I'd like to resolve as many obvious divergences as possible and then include in the report.
14:53:21 [francois]: Russell: I'm not necessarily favoring an API the way you propose [scribe missed precise concern]
14:54:25 [francois]: Clarke: when something is discovered, it calls a callback. I found it useful to combine things, but you could have your user agent to do otherwise. The basic idea of having discovery "routines" that calls a callback is pretty generic and doesn't predict any specific implementation.
14:54:30 [francois]: ... The same goes for request.
14:54:43 [francois]: ... If you want one callback for zeroconf, one for DLNA, etc. that's fine.
14:55:00 [kaz]: q+ to ask igarashi as well about his opinon, because he also mentioned Sony has similar idea to Opera
14:55:10 [francois]: Russell: something like REST call, does that require a callback?
14:55:48 [francois]: Clarke: what happens is that you send a message, and when you get a response, which is asynchronous, the callback gets called. A single routine could handle all your REST responses, or different routines could be used.
14:55:59 [francois]: ... Still, you send a request, then get a response.
14:56:41 [francois]: Russell: I might suggest that you write this in "here's the usage scenario" instead of providing an IDL, not very consistent with the way we've approaches other use cases.
14:56:52 [francois]: Giuseppe: The goal is more to capture how this could be implemented.
14:57:28 [francois]: ... It is not to become the specification, it's merely meant to suggest how an API could be defined.
14:58:47 [francois]: Russell: I suspect there is a use case knocking around in this document. I would encourage the writing of a use case based on this document. One concern is what happens to one device discovered with different methods? Is there a way to say that this is the same?
14:58:59 [francois]: ... I think it raises some interesting questions.
14:59:34 [francois]: Clarke: It's one way to implement the requirements triggered by the other use cases. It's certainly not the only one.
15:00:07 [francois]: ... I'm uncertain how this should be communicated to any working group that addresses these requirements.
15:00:51 [francois]: Giuseppe: my view on this is that we need to make sure the discussions are reflected on this document, then we can decide to publish it along with the requirements document to the intention of a working group.
15:01:13 [francois]: ... If it's already covered by another document, e.g. by Opera's proposal, then maybe we can drop it.
15:01:26 [francois]: ... We need to have opinions on this.
15:01:59 [francois]: ... The same applies to the Security document, actually.
15:02:17 [Zakim]: -mav
15:02:18 [francois]: Clarke: I'll try to write something that tries to align CableLabs and Opera's proposals.
15:02:23 [Zakim]: -David_Mays
15:02:26 [davidmays]: davidmays has left #webtv
15:02:27 [francois]: Giuseppe: ok, running out of time, here.
15:02:52 [kaz]: q-
15:02:59 [Zakim]: -Clarke_Stevens
15:03:01 [francois]: [call adjourned]
15:03:02 [Zakim]: -aizu
15:03:03 [Zakim]: -Russell_Berkoff
15:03:05 [Zakim]: -MattH
15:03:06 [Zakim]: -giuseppe
15:03:06 [Zakim]: -francois
15:03:13 [Zakim]: -Kazuyuki
15:03:17 [giuseppe]: I hope you could hear what I was saying....
15:04:05 [giuseppe]: I was using skype, next time I'll use the phone
15:04:53 [giuseppe]: yep
15:05:05 [giuseppe]: well review before and approve during
15:08:14 [Zakim]: disconnecting the lone participant, igarashi, in UW_WebTVIG(Home Net)10:00AM
15:08:16 [Zakim]: UW_WebTVIG(Home Net)10:00AM has ended
15:08:19 [Zakim]: Attendees were Kazuyuki, giuseppe, Russell_Berkoff, MattH, francois, +1.215.286.aaaa, David_Mays, aizu, Clarke_Stevens, igarashi, +1.650.483.aabb, mav
15:08:35 [giuseppe]: francois, thanks or scribing
15:11:44 [kaz]: s/we can review it next time and approve it./we can review it before the f2f meeting and approve it during the meeting./
15:11:50 [kaz]: rrsagent, draft minutes
15:11:50 [RRSAgent]: I have made the request to generate http://www.w3.org/2011/08/02-webtv-minutes.html kaz
15:11:53 [MattH]: MattH has left #webtv
15:22:28 [giuseppe]: kaz do you want me to reply to the TTA guy or are you going to do it?
16:22:25 [giuseppe]: giuseppe has joined #webtv
16:31:48 [francois]: RRSAGent, bye
16:31:48 [RRSAgent]: I see 9 open action items saved in http://www.w3.org/2011/08/02-webtv-actions.rdf :
16:31:48 [RRSAgent]: ACTION: giuseppe to integrate ISSUE-20 in requirements spec [1]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-08-28
16:31:48 [RRSAgent]: ACTION: giuseppe to integrate ISSUE-21 in requirements spec [2]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-13-38
16:31:48 [RRSAgent]: ACTION: Giuseppe to integrate ISSUE-22 in requirements spec. [3]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-18-28
16:31:48 [RRSAgent]: ACTION: giuseppe to integrate ISSUE-23 in requirements spec. [4]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-23-48
16:31:48 [RRSAgent]: ACTION: Giuseppe to integrate ISSUE-26 in requirements spec [5]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-31-03
16:31:48 [RRSAgent]: ACTION: Giuseppe to integrate ISSUE-27 in requirements spec [6]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-34-37
16:31:48 [RRSAgent]: ACTION: Giuseppe to integrate ISSUE-28 in requirements spec [7]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-36-52
16:31:48 [RRSAgent]: ACTION: Giuseppe to integrate ISSUE-29 in requirements spec [8]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-38-16
16:31:48 [RRSAgent]: ACTION: Russell to see if ISSUE-14 and ISSUE-30 can be merged [9]
16:31:48 [RRSAgent]: recorded in http://www.w3.org/2011/08/02-webtv-irc#T14-45-26
16:31:50 [francois]: zakim, bye
16:31:50 [Zakim]: Zakim has left #webtv