Re: Conference call agenda, October 18 2016

Dear all,

I had to schedule another call today however see some of my thoughts inline:

Am 14.10.16, 16:16 schrieb "Chris Needham" <chris.needham@bbc.co.uk>:

    Hi all,
    
    Here is the agenda and connection details for the next TV Control Working Group meeting.
    
    Tuesday, October 18, 2016
    9:00 am | Eastern Daylight Time (New York, GMT-04:00) | 1 hr
    
    http://www.timeanddate.com/worldclock/fixedtime.html?msg=TV-Control-API&iso=20161018T13&ah=1

    
    # Agenda
    
    1. Welcome
    
    * Agenda review, scribe selection
    
    2. Group status and request for editorial support


I would volunteer, for  editing in the Radio stuff.  

    
    3. Open issues
    
    * The TVSource and TVTuner objects (https://github.com/w3c/tvcontrol-api/issues/4)
    
    * API changes to support radio (https://github.com/w3c/tvcontrol-api/pull/14)

Once the WG agrees on the prefix to use, most of the changes I proposed could be made (with the new prefix then) easily. Regarding the two additional  interfaces (ChannelAttributes and Application) I am free to rename to better suited names as I had the feeling, the names I’ve choosen were not good. 

Eg. ChannelParameters (for ChannelAttributes) 
ChannelDataComponent (for Applications). I agree that Application is a to misleading term for components such as Slideshow, Dynamiclabel …. 
    
    4. Application types
    
    Which API features are needed by each application type?
    
    https://www.w3.org/wiki/TV_Control/Application_Types



Type1: ok 

Type2: Two aspects here, the signalisation  (AIT or other means) could be handled by my ChannelDataComponent Interface proposal , whether the implementation is supporting such applications (in case of DVB Services  Hbbtv, or Webcontent using the W3C API) is an implementation issue. However when such applications are supported, we should mandate, that this application are the “first citizens” on such a device. I mean no other (lesser prioritized ) application can overdraw/overrule the broadcasters signalled applications. 

Type3: I would say, the “surrounding”webpage is not allowed to break the integrity of the broadcast signal. This means, no restrictions in presentation, no overly and  no “application control”    other than Type2 applications if signalled.



If my other call is finished early I’ of course will try to dial into the W3C telco.

Best regards

Alex
 5. AOB
    
    # Connection details
    
    To join the meeting from a browser:
    https://mit.webex.com/mit/j.php?MTID=maa1395b6856d226b69a8c230cc6bbc51

    
    To join the meeting from a WebEx application:
    Meeting number: 646 942 941
    Meeting password: see https://lists.w3.org/Archives/Member/w3c-archive/2016May/0149.html (member-only)
    
    To join by phone: +1-617-324-0000 US Toll Number
    
    IRC Channel: #tvapi on irc.w3.org, port 6665, or http://irc.w3.org/?channels=#tvapi

    
    Best regards,
    
    Chris (WG Chair)
    
    
    -----------------------------
    http://www.bbc.co.uk

    This e-mail (and any attachments) is confidential and
    may contain personal views which are not the views of the BBC unless specifically stated.
    If you have received it in
    error, please delete it from your system.
    Do not use, copy or disclose the
    information in any way nor act in reliance on it and notify the sender
    immediately.
    Please note that the BBC monitors e-mails
    sent or received.
    Further communication will signify your consent to
    this.
    -----------------------------

Received on Tuesday, 18 October 2016 11:01:56 UTC