13:00:31 RRSAgent has joined #tvapi 13:00:31 logging to http://www.w3.org/2015/03/17-tvapi-irc 13:00:42 Hi Kaz 13:00:49 zakim, this will be tv 13:00:49 ok, kaz, I see WEBT_TVAPICG()9:00AM already started 13:00:58 zakim, call kazuyuki-617 13:00:58 ok, kaz; the call is being made 13:01:00 + +44.303.040.aaaa 13:01:01 +Kazuyuki 13:01:21 zakim, who is here? 13:01:21 On the phone I see ??P0, +44.303.040.aaaa, Kazuyuki 13:01:23 On IRC I see RRSAgent, Zakim, ddavis, cpn, seanlin, kaz, ted, trackbot 13:01:28 +??P11 13:01:31 zakim, ??P11 is me 13:01:31 +ddavis; got it 13:01:37 zakim, aaaa is cpn 13:01:37 +cpn; got it 13:01:44 Bin_Hu has joined #tvapi 13:02:43 + +1.650.946.aabb 13:02:53 zakim, aabb is me 13:02:53 +Bin_Hu; got it 13:03:01 +Paul_Higgs 13:03:06 zakim, who is here? 13:03:06 On the phone I see ??P0, cpn, Kazuyuki, ddavis, Bin_Hu, Paul_Higgs 13:03:08 On IRC I see Bin_Hu, RRSAgent, Zakim, ddavis, cpn, seanlin, kaz, ted, trackbot 13:03:19 -??P0 13:04:42 +??P17 13:04:53 zakim, ??P17 is sean 13:04:53 +sean; got it 13:05:37 scribenick: cpn 13:05:39 Scribe: Chris 13:05:52 Meeting: TV Control API CG 13:06:03 Present: Bin, Kaz, Daniel, Chris, Paul 13:06:08 Agenda: https://www.w3.org/community/tvapi/wiki/Main_Page/Agenda_Telco_Mar_17_2015 13:06:36 topic: Summary of TV Developer Meetup in Tokyo 13:06:37 Topic: Developer meetup 13:07:07 Daniel: We had a 2 day developer meetup, looking at the TV API 13:07:18 ... from a Hybridcast and TV API point of view 13:07:20 rrsagent, make log public 13:07:23 rrsagent, draft minutes 13:07:23 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html kaz 13:07:42 ... We looked at things in Hybridcast not supported by the TV API 13:08:29 ... Firstly, the triggered interactive overlay. Could this be split into two requirements: a trigger requirement, and an overlay requirement 13:08:49 Paul_Higgs has joined #tvapi 13:08:57 ... There could be two kinds of triggers, one with a pre-defined time, and one that is generated live 13:09:25 ... For those with pre-defined times, could the in-band resource track spec be used? 13:09:43 http://www.w3.org/2014/05/28-webtv-minutes.html#item05 13:11:40 Bin: There can be relative time stamps encoded in the stream for triggering events 13:12:12 Paul: The service provider can signal events, say every 10 minutes 13:12:23 s/Paul: The/Bin: The/ 13:13:19 Paul: There is also an alarm clock API 13:13:35 Daniel: Can out of band triggers be supported by server sent events? 13:13:41 https://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping 13:14:22 Daniel: Hybridcast does not have a channel change event, as the application is closed on changing channel 13:15:34 Paul: Hybridcast and HbbTV are essentially channel-bound, so changing channel replaces the interactive environment, to be replaced with a new one. 13:16:10 ... With the Open IPTV Forum specs, the application persists, this is described in the application lifecycle model in the DAE 13:16:32 s/replaces the/discards the/ 13:17:19 Daniel: The group was wondering whether the TV control API should converge these two approaches 13:18:23 Paul: The issue of a security model was raised on the mailing list, and there are privacy concerns too. 13:18:52 Daniel: We discussed using watermark fingerprint triggers for synchronising alternate streams. 13:20:15 Bin: With the supplemental triggers, these are optional, if present they should be surfaced by the API 13:21:00 Bin: We would have to define the content type and data structures for these triggers, to identify these as trigger metadata 13:21:05 rrsagent, draft minutes 13:21:05 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html kaz 13:21:30 Bin: Some fields are mandatory, such those controlling the as start time and end time/duration of the trigger 13:21:34 Chair: Bin 13:21:52 s/topic: Summary of TV Developer Meetup in Tokyo// 13:21:55 rrsagent, draft minutes 13:21:55 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html kaz 13:22:12 s/Topic: Developer meetup/Topic: Summary of TV Developer Meetup in Tokyo/ 13:22:27 rrsagent, draft minutes 13:22:27 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html kaz 13:22:46 Type: video/x-iptvf-broadcast 13:22:47 Daniel: It would help to write down more of this detail in the requirements 13:23:17 13:23:37 http://www.w3.org/TR/mediacapture-streams/#idl-def-MediaStream 13:23:51 Daniel: Regarding integration with HTML5 audio and video elements, Hybridcast a specific content-type, with parameters not available in the media stream 13:24:20 Paul: There is also a different state machine, when comparing HTML5 media with OIPF 13:25:31 Paul: Looking at combining the W3C specs, we've found pausing live TV in a media element would require reinitialising the media element 13:26:16 Paul: Chris suggested maybe allowing buffering with MediaStreams, but do we define that or put this to that group 13:26:47 Daniel: Emergency notifications are implemented by a separate system, EWS, not within Hybridcast 13:26:53 aldafu has joined #tvapi 13:27:10 + +49.303.aacc 13:27:19 Zakim: aacc is me 13:27:37 Present+ aldafu 13:28:07 Daniel: There is an earthquake prediction service, which may need to be triggered differently 13:29:12 Paul: In the US there is a classification, different alerts have different priorities 13:30:27 Daniel: Regarding the EPG, we have a getProgrammes method in the mapping table, which takes an options object 13:30:49 ... our API should allow more filtering options, such as by type of content (movies, sport) 13:31:02 ... also, get EPG by channel 13:31:34 ... the duration option is confusing, as its the time range for the search, maybe we should change this to endTime? 13:33:17 Paul: There are lots of ways to search, so with TV Anytime, we have attribute pairings, more schema-less to allow more flexible data models 13:33:35 Daniel: The general view was to allow more ways to search for programes 13:33:48 s/programes/programmes/ 13:34:07 https://w3c.github.io/tvapi/spec/#h-tvprogram-interface 13:35:04 Daniel: The TVProgram interface, should there be both a short description and a long description, is it a satellite or terrestrial programme. 13:35:42 ... The getAudioLanguages and getSubtitleLanguages methods were felt to be too restrictive. There can be alternate commentaries but in the same language. 13:36:14 ... An API like getAudioTracks might be more flexible, similar for subtitles: getSubtitleTracks 13:37:41 ... The satellite/terrestrial could be added to the TVChannelType enum 13:38:08 ... The isFree flag on the TVChannel could be added to the TVProgramme object, for free channels that contain some paid programmes 13:39:24 ... Regarding parental control, this could be done at the programme or at the system level, we may need to clarify our requirements 13:39:49 Daniel: We'll share our notes from the meeting 13:40:02 Paul: Did the group identify anything missing? 13:40:52 Daniel: Maybe more device information, with properties such as manufacturer, but we need to identify requirements. 13:42:08 Bin: Which group is working on the in band tracks? 13:42:11 https://www.w3.org/community/inbandtracks/ 13:42:55 http://dev.w3.org/html5/html-sourcing-inband-tracks/ 13:43:12 Paul: This is looking at mappings from ISDB, ATSC etc to tracks associated with a video element 13:44:56 Bin: I have an interest in the encoding mechanism, for example, a raw A/V stream from the studio, how do we add the triggers and encode them within the stream. Which is the easiest way to do this during encoding? 13:46:34 Bin: The dataCue can provide an abstraction over the underlying transport method 13:47:22 Paul: HbbTV defines stream events. There's a method addStreamEventListener. How it's encoded in the transport stream would be specified by DVB 13:50:32 Daniel: One other comment, more for the multi device timing comnunity group: HTML5 needs a more accurate way to reference the timeline, e.g., for ad insertion. for example, the timeupdate event is only generated every 250ms 13:50:53 Daniel: That's all our feedback, we had a good useful discussion today. 13:51:11 Topic: Review of action items 13:51:23 http://www.w3.org/community/tvapi/track/actions/open 13:51:57 ACTION: ddavis to share wiki page containing feedback from Japan TV dev meetup 13:51:57 Created ACTION-28 - Share wiki page containing feedback from japan tv dev meetup [on Daniel Davis - due 2015-03-24]. 13:52:55 Alex: with action 23, the feedback and discussion about action 24 is related to this, in particular the background task for recording 13:53:20 Bin: So we can close action 23 13:53:53 Bin: Paul and Chris have reported their findings for actions 24 and 25, on recording and timeshifting 13:54:10 action-23? 13:54:10 action-23 -- Alexander Futász to Email the mailing list regarding the recording.series requirement and proposed solutions -- due 2015-02-24 -- CLOSED 13:54:10 http://www.w3.org/community/tvapi/track/actions/23 13:54:17 action-24? 13:54:17 action-24 -- Paul Higgs to Look at the media capture and streams api and compare against our recording and timeshifting requirements -- due 2015-04-14 -- OPEN 13:54:17 http://www.w3.org/community/tvapi/track/actions/24 13:54:20 action-25? 13:54:20 action-25 -- Chris Needham to Look at the timeshifting requirements and the html video element -- due 2015-03-17 -- OPEN 13:54:20 http://www.w3.org/community/tvapi/track/actions/25 13:57:04 Paul: We need to ensure our API meets regulatory requirements regarding background workers, as TV devices go into standby mode 13:57:28 Paul: It would be useful to see some examples of how the various APIs fit together 13:58:11 what I call the alarm clock API is http://www.w3.org/2012/sysapps/web-alarms/ 14:00:39 sorry, I have a hard stop now - I think this call is just scheduled for 1 hour! 14:00:59 -Paul_Higgs 14:04:08 Bin: For action 25 (time shifting), we can do some more investigation, look again at our requirements, also we should understand the rationale for preventing buffering of MediaStreams. We should do this before proposing any changes. 14:05:12 Action: Chris to look further into timeshifting and MediaStream API rationale 14:05:13 Created ACTION-29 - Look further into timeshifting and mediastream api rationale [on Chris Needham - due 2015-03-24]. 14:05:58 Bin: we'll leave actions 26 and 27 open, and hopefully report on these next time 14:06:12 action-26? 14:06:12 action-26 -- Bin Hu to Contact sean and add emergency alert requirements to the spec -- due 2015-02-24 -- OPEN 14:06:12 http://www.w3.org/community/tvapi/track/actions/26 14:06:17 action-27? 14:06:17 action-27 -- Bin Hu to Work on triggered interactive overlay requirements -- due 2015-02-24 -- OPEN 14:06:17 http://www.w3.org/community/tvapi/track/actions/27 14:06:37 - +49.303.aacc 14:06:39 -Kazuyuki 14:06:40 -Bin_Hu 14:06:42 -cpn 14:06:44 -sean 14:06:45 -ddavis 14:06:45 WEBT_TVAPICG()9:00AM has ended 14:06:45 Attendees were +44.303.040.aaaa, Kazuyuki, ddavis, cpn, +1.650.946.aabb, Bin_Hu, Paul_Higgs, sean, +49.303.aacc 14:07:50 Present: Alex 14:08:05 [ adjourned ] 14:08:10 rrsagent, draft minutes 14:08:10 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html cpn 14:08:45 Present: Bin, Kaz, Daniel, Chris, Paul, Alex 14:08:54 rrsagent, draft minutes 14:08:54 I have made the request to generate http://www.w3.org/2015/03/17-tvapi-minutes.html cpn 14:40:20 cpn has left #tvapi 15:06:50 Zakim has left #tvapi