13:16:28 <RRSAgent> RRSAgent has joined #tvapi
13:16:28 <RRSAgent> logging to http://www.w3.org/2016/07/26-tvapi-irc
13:16:30 <Zakim> Zakim has joined #tvapi
13:16:42 <kaz> Meeting: TV Control Working Group
13:16:45 <kaz> Chair: Chris
13:18:17 <cpn> Present: YoungSun, Yann, Chris
13:18:45 <ryandavis> can someone remind me what the password is?
13:20:08 <cpn> Present+ Alex, Ryan
13:23:28 <cpn> cpn: Runs through the agenda
13:23:42 <cpn> topic: Radio use cases
13:23:51 <cpn> https://www.w3.org/wiki/TV_Control/Use_Cases
13:24:06 <cpn> cpn: Jean Pierre and I have updated some of the radio uses
13:29:20 <cpn> cpn: There are some new requirements, around content redistribution and permissions for web sites to present broadcast content
13:29:51 <cpn> ... Also for the use of schema.org metadata, both in publishing and consumption of this data
13:30:07 <cpn> alex: we support these requirements for content redistribution
13:30:20 <kaz> i/Runs through/scribenick: cpn/
13:30:26 <kaz> rrsagent, make log public
13:30:30 <kaz> rrsagent, draft minutes
13:30:30 <RRSAgent> I have made the request to generate http://www.w3.org/2016/07/26-tvapi-minutes.html kaz
13:31:09 <cpn> alex: there are also new radio requirements: for tuning, channel scan, presentation using <audio>, registering for change notifications
13:31:14 <cpn> ... control of service playback and status
13:32:25 <cpn> ... also service metadata, we should be able to deliver basic metadata, service ids, genres, also technical metadata eg, bearer, signal quality, and registering changes in these
13:32:36 <cpn> ... it's basically the same as we have for TV in the API
13:33:16 <cpn> ... something new is the use cases for radio applications: we have dynamic label, or radio text, and slideshow
13:33:41 <cpn> ... the API should be able to register callbacks for these dynamic label and slideshow events
13:34:03 <cpn> ... this is an important use case from our point of view, to deliver title and artist information
13:34:29 <cpn> ... the API should also deliver what I call MOT header information, including click-through URLs on images
13:35:09 <cpn> ... lastly, the EPG use cases look OK, and in principle it's the same as TV
13:35:52 <cpn> ... there are other applications besides dynamic label and slideshow (eg, journaline), but i think those are the most import
13:36:50 <cpn> ryan: i agree with this, and will see if we can add anything
13:37:42 <cpn> ... the genivi media manager has requirements along these lines, for auto
13:38:27 <cpn> cpn: alex, have you been thinking about the necessary changes to the api?
13:38:46 <cpn> alex: yes, but how best to do that - github issue?
13:39:11 <cpn> ... at the moment we have TVManager, TVSource, TVTuner, and why we have each of these
13:39:29 <cpn> ... the idea of having a tuner and a source seems ok
13:40:12 <cpn> ... for the radio use case, do we stick with the naming - TVSource, TVTuner, or should we use a more agnostic naming convention
13:41:46 <cpn> ... i could live with the existing approach, but looking at TVSourceType we'd need to add some non-TV sources here, e.g, T-DMB, needed to support DAB, FM, DRM, HD Radio
13:42:57 <cpn> ... the next change would be in TVChannel, how should we architect the API? Integrating radio may not be the best approach, some of the technical attributes don't make sense for radio
13:43:11 <cpn> ... so i think we need a distinction between a TV channel and a radio channel
13:44:54 <cpn> ... I could write this up and put it into GitHub
13:46:20 <cpn> ryan: i like the current setup with manager, tuner, etc
13:46:38 <cpn> a source could be a tuner with a collection of APIs
13:47:32 <cpn> alex: the existing API models what's physically going on, a TV can have a tuner with DVB-C and DVB-T sources
13:49:34 <cpn> cpn: i think i'd us to rename the objects to make them more generic
13:50:21 <cpn> alex: for the channel interface, we could have a base interface, then inherit from this to get TV and radio specialisation
13:51:56 <cpn> cpn: i think describing the proposed changes on GitHub is the next step
13:52:04 <cpn> alex: i'm happy to do that
13:52:33 <cpn> topic: TPAC planning
13:52:49 <cpn> cpn: we have the meeting scheduled for the tuesday at TPAC
13:53:22 <cpn> ... does any want to be able to attend remotely?
13:53:41 <cpn> alex: i may want to, yes
13:54:07 <cpn> ... ok, i'll work with w3c staff to organise that
13:55:50 <cpn> ryan: i won't be attending, but i could also join remotely
14:02:09 <cpn> cpn: i'd like for use to discuss the architectural issues with the API at TPAC, such as the open web vs the device oriented nature of the API
14:02:21 <ryandavis> https://www.w3.org/auto/security/wiki/ASP_TF
14:03:03 <cpn> cpn: i'll try to send out a proposed agenda for the F2F as soon as possible, so remote people can plan when to join
14:03:28 <cpn> Topic: GitHub issues
14:05:57 <cpn> cpn: i had an action from the last meeting to write some introductory text
14:05:57 <cpn> https://github.com/w3c/tvcontrol-api/pull/12
14:06:56 <cpn> cpn: suggestions for improving this would be very welcome
14:07:48 <cpn> cpn: francois and i have been putting issues into GitHub: https://github.com/w3c/tvcontrol-api/issues
14:08:12 <cpn> ... please add your views or suggestions as comments to these
14:08:18 <ryandavis> here is the link for the Media Manager from Genivi to look over https://at.projects.genivi.org/wiki/display/PROJ/Media+Manager
14:08:21 <cpn> ... or suggest changes to the spec text itself
14:11:33 <cpn> Topic: AOB
14:11:46 <cpn> Yann: I have a particular issue, which I'll raise on GitHub
14:12:15 <cpn> Hyojin: I'll discuss the radio changes internally and come back to the WG if we have any concerns
14:13:32 <cpn> cpn: next call will be August 23
14:13:59 <cpn> - Adjourned -
14:14:17 <cpn> rrsagent, draft minutes
14:14:17 <RRSAgent> I have made the request to generate http://www.w3.org/2016/07/26-tvapi-minutes.html cpn
14:33:47 <cpn> Present+ Hyojin
14:33:50 <cpn> rrsagent, draft minutes
14:33:50 <RRSAgent> I have made the request to generate http://www.w3.org/2016/07/26-tvapi-minutes.html cpn
15:38:21 <kaz> kaz has joined #tvapi
17:01:24 <Zakim> Zakim has left #tvapi