12:58:52 RRSAgent has joined #tvapi 12:58:52 logging to http://www.w3.org/2015/08/04-tvapi-irc 12:58:55 Bin_Hu has joined #tvapi 13:00:29 seanlin has joined #tvapi 13:02:36 skim13 has joined #tvapi 13:03:26 Present: Kaz, Bin, Chris, SungHei 13:03:45 Present: Kaz, Bin, Chris, SungHei, Sean 13:04:38 Present: Kaz, Bin, Chris, SungHei, Sean, Paul 13:06:02 Scribe: Chris 13:06:09 scribenick: cpn 13:06:23 Topic: Review of action items 13:06:29 action-32? 13:06:29 action-32 -- Kazuyuki Ashimura to Add column to gap analysis/requirements table for genivi ideas -- due 2015-05-19 -- OPEN 13:06:29 http://www.w3.org/community/tvapi/track/actions/32 13:06:46 Kaz: I've done this, yes 13:07:08 Bin: Do you plan to add any further analysis? 13:07:36 Kaz: I've talked to participants in the automotive group, but we'd need some more time to do the gap analysis 13:07:49 close action-32 13:07:49 Closed action-32. 13:08:02 action-36? 13:08:03 action-36 -- Chris Needham to Look at the requirements from the media pipeline tf -- due 2015-07-14 -- OPEN 13:08:03 http://www.w3.org/community/tvapi/track/actions/36 13:08:28 Paul_Higgs has joined #tvapi 13:08:52 http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements 13:09:17 -> https://lists.w3.org/Archives/Public/public-tvapi/2015Jun/0012.html Kaz's initial survey (FYI) 13:09:46 cpn: parental control is covered 13:09:54 ... adaptive media is also covered 13:10:11 ... content protection is covered by our new work done by SungHei, etc. 13:11:25 Kaz: I agree with Chris, but I suggest updating our own requirements based on the MPTF requirements, there could be some good suggestions there 13:11:41 ... also their accessibility use cases 13:12:08 Chris: I can look at these and update the requirements table 13:12:59 Bin: We should review the updated requirements before we change our spec 13:13:23 ... We don't want this to impact us having a stable spec for TPAC 13:13:39 ... If there are changes, we can address them in the next version 13:14:03 i/parental/scribenick: kaz/ 13:14:12 i/agree with/scribenick: cpn/ 13:14:28 action-37? 13:14:28 action-37 -- Sean Lin to Update the progress measurement table for recording, timeshifting, and triggered overlays -- due 2015-07-14 -- OPEN 13:14:28 http://www.w3.org/community/tvapi/track/actions/37 13:14:51 Sean: I have updated the table, yes 13:15:32 Bin: The main gaps now are CAS and parental control 13:15:48 close action-37 13:15:48 Closed action-37. 13:15:52 action-38? 13:15:52 action-38 -- Sung Hei Kim to Propose an api spec for conditional access systems -- due 2015-07-14 -- OPEN 13:15:52 http://www.w3.org/community/tvapi/track/actions/38 13:16:29 Sung-Hei: I need some more time to look at this. 13:17:40 ... Do applications need knowledge of CI cards? I wonder if we need to change the requirements, to support more useful events such as service not subscribed, resource not available in the API? 13:18:15 ... What was the intention behind the existing requirements regarding CI cards, and what information can be provided? 13:19:41 Paul: There are some things that you need to know, the cards have identifiers, and capabilities, so the app can enumerate installed cards, and see which DRM IDs are available 13:19:57 Sung-Hei: Are you thinking that a set-top box has multiple cards? 13:20:28 Paul: Yes, I've seen that, some cable cards in the US are multi-mode, supporting multiple simultaneous decryption systems 13:20:48 Sung-Hei: In my country there's generally only one card used 13:20:57 Paul: In general that's true 13:21:59 ... Each CI card does a different job, eg for a terrestrial broadcast line-up, there might be some free-to-air channels, some channels protected with one system, other channels protected by another, hence the need for multiple cards 13:22:24 ... The type of CAS is signalled in the broadcast stream, then the application needs to determine if any of the installed cards can handle it 13:22:59 Sung-Hei: Do we need an API that allows applications to determine whether content is unable to be decrypted? 13:24:06 Paul: Yes. For example, pay per view channels have a free component, then a programme starts that is scrambled. In that case, there'd be an error raised, as in OIPF 13:24:40 Sung-Hei: So I'd add a requirement to inform the web app of any protection-related errors 13:24:52 ... This could be done possibly as part of the TVSource 13:25:43 Bin: Do you think we'd be able to have a proposal by next meeting, or should we defer the requirement to the next version of the spec? 13:26:08 Sung-Hei: I need some more time, yes 13:26:22 Bin: Let's leave this item open until next meeting 13:26:57 Kaz: Regarding the number of CAS cards, some Japanese TV records have 8 mini-card slots, one each for a specific channel 13:27:19 ... So we might need to have a parameter to identify them 13:28:26 Paul: In the US, there is a cable card, but the functionality is often built into the set-top box 13:28:47 ... The card belongs to the service provider, giving access to their service 13:29:03 Sung-Hei: That clarifies the requirements, thank you 13:29:42 Bin: Sean has done good work on recording and timeshifting, updating the spec 13:29:56 ... According to the progress measurement, most of the gaps have been filled 13:30:25 ... But there are a few gaps in tuner requirements, some in channel requirements, some in programme requirements, etc 13:30:58 ... What should we do to resolve these? 13:31:27 Sean: The tuner and channel scan gaps are already supported, and reflected in progress measurement 13:32:41 ... So there are 5 gaps in programme requirements and 1 in programme requirements 13:33:16 Paul: Looking at these gaps, it looks like these could be done at application-level 13:34:09 ... channel.search is more related to the programmes in the channel, so we should leave that open 13:34:57 ... channel.tracks is important for multiple audio tracks 13:35:32 Bin: So which of these should be supported in the API? 13:36:26 Paul: The channel.search requirement mentions "channels/programmes", there may be an overlap with eg the EPG requirements 13:38:36 Bin: Which of these should we address, and what can we defer? 13:39:37 Paul: I'd prioritise the parental controls above the recording and timeshifting, they should be core as the spec won't be usable without them 13:41:00 Paul: Some is straightforward, some is region-specific, eg, each region has different rating schemes 13:41:31 ... Locking and unlocking parental rating is important, but I'll try to take a look at those 13:42:46 Bin: Maybe we can have a general categorisation of channels, and a different API implementation for different regions 13:43:46 Paul: The API can just list the ratings, but the application may not know what to do with them 13:44:36 Bin: The application implements the regulatory requirements, and presenting to the user in the appropriate way, offering option to unlock 13:45:10 Paul: I think the controls would be at the TVManager level in the API 13:46:13 Sean: As far as I know, the parent configures channels with an access code to unlock them 13:46:47 Paul: In Germany, a public channel can show G rated content, and in the evening it can switch to R rated 13:47:48 Bin: This is why we have two methods: channel-based unlocking, and providing list of ratings. We can make the ratings method general, to allow applications to implement the logic and present to the user 13:48:11 ... The application will also control the access to the R channels 13:48:34 ... This approach simplifies the spec, as it just provides information to the application 13:48:57 Bin: Paul, would you be able to specify this? 13:49:07 Paul: I'll have a look into it 13:49:33 action: Paul to look into parental control 13:49:33 Created ACTION-39 - Look into parental control [on Paul Higgs - due 2015-08-11]. 13:50:20 action: Paul to look at existing requirement gaps for channel and programme data 13:50:21 Created ACTION-40 - Look at existing requirement gaps for channel and programme data [on Paul Higgs - due 2015-08-11]. 13:52:05 Chris: My time is limited at the moment, but I'll try to respond on the mailing list 13:52:46 action-40 due 2015-09-01 13:52:46 Set action-40 Look at existing requirement gaps for channel and programme data due date to 2015-09-01. 13:53:00 I will do some drafting to the mailing list for initial comment 13:53:09 action-39 due 2015-09-01 13:53:09 Set action-39 Look into parental control due date to 2015-09-01. 13:53:29 action-36 due 2015-09-01 13:53:29 Set action-36 Look at the requirements from the media pipeline tf due date to 2015-09-01. 13:53:38 action-38 due 2015-09-01 13:53:38 Set action-38 Propose an api spec for conditional access systems due date to 2015-09-01. 13:54:13 Topic: AOB 13:54:30 Paul: Are you happy with the discussion on the mailing list 13:54:50 ... Chris made a comment this morning 13:55:33 Sean: I haven't responded, but I'll update the spec. I'd expect to have some follow-up discussion, so I'll keep an eye on it 13:56:04 ... We're discussing programme series recording 13:56:58 Bin: Regarding TPAC, Daniel mentioned that the Web and TV group are working on the agenda 13:57:52 Kaz: The biggest topics are GGIE and the control API, so we can discuss with the IG chair and Glenn from GGIE how to share the time 13:58:50 Paul: I've heard about the timed media WG, but I don't know how this group relates to that 13:59:29 http://w3c.github.io/charter-html/timed-media-wg.html 14:00:07 Kaz: This group will cover MSE and EME, so we should work with them 14:00:35 -> https://lists.w3.org/Archives/Member/w3c-ac-members/2015JulSep/0026.html Web Platform and Timed Media WG proposed Charters (member-only) 14:01:01 s/with them/with them once that group's charter is approved/ 14:01:26 seanlin has left #tvapi 14:01:44 skim13 has left #tvapi 14:03:08 Bin: Meeting adjourned 14:03:35 rrsagent, make log public 14:03:41 rrsagent, draft minutes 14:03:41 I have made the request to generate http://www.w3.org/2015/08/04-tvapi-minutes.html cpn 14:04:15 Chair: Bin Hu 14:04:18 rrsagent, draft minutes 14:04:18 I have made the request to generate http://www.w3.org/2015/08/04-tvapi-minutes.html cpn 14:44:31 Meeting: TV Control API CG 14:44:34 rrsagent, draft minutes 14:44:34 I have made the request to generate http://www.w3.org/2015/08/04-tvapi-minutes.html cpn 15:18:58 jcverdie has joined #tvapi 15:25:26 Zakim has left #tvapi 15:26:53 jcverdie has joined #tvapi 15:29:15 jcverdie_ has joined #tvapi 16:00:40 jcverdie has joined #tvapi 16:03:25 jcverdie_ has joined #tvapi 16:11:17 jcverdie has joined #tvapi 16:14:20 nigel_ has joined #tvapi 16:32:43 jcverdie_ has joined #tvapi 21:31:43 kaz has joined #tvapi