RE: tvapi-ACTION-40: Look at existing requirement gaps for channel and programme data

No problem, lets discuss on e-mail as necessary before the next call

From: HU, BIN [mailto:bh526r@att.com]
Sent: Thursday, August 20, 2015 2:39 PM
To: Paul Higgs; TV Control API Community Group
Subject: RE: tvapi-ACTION-40: Look at existing requirement gaps for channel and programme data

Great work, and thank you Paul.

Bin

From: Paul Higgs [mailto:paul.higgs@ericsson.com]
Sent: Thursday, August 20, 2015 10:44 AM
To: TV Control API Community Group
Subject: RE: tvapi-ACTION-40: Look at existing requirement gaps for channel and programme data


Gap analysis for requirements “not supported” as of 18 August 2015 - https://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping




Req.ID


Requirement


Notes


channel.search


The API SHALL be able to provide the webapps with the functions of sorting, searching, and filtering the channel/program list, including but not limited to:


The current TVSource.getChannels()<http://w3c.github.io/tvapi/spec/#widl-TVSource-getChannels-Promise-sequence-TVChannel> API provides a sequence of TVChannel<http://w3c.github.io/tvapi/spec/#idl-def-TVChannel> objects. Assuming an idl <sequence> maps to a Javascript Array, then the application has access to all channels and can query as necessary with suitable iterators


channel.filter


filtered based on rating information for Parental Control


The current TVSource.getChannels()<http://w3c.github.io/tvapi/spec/#widl-TVSource-getChannels-Promise-sequence-TVChannel> API provides a sequence of TVChannel<http://w3c.github.io/tvapi/spec/#idl-def-TVChannel> objects. If an approach as outlined in the follow up to ACTION-39 is implemented, then this API can provide a subset of channels if Parental Control is currently active on the device

-          This can help stop unrated viewers reading descriptions and viewing poster art of rated programs


channel.sort


sorted based on program start time, name etc


The current TVSource.getChannels()<http://w3c.github.io/tvapi/spec/#widl-TVSource-getChannels-Promise-sequence-TVChannel> API provides a sequence of TVChannel<http://w3c.github.io/tvapi/spec/#idl-def-TVChannel> objects. Assuming an idl <sequence> maps to a Javascript Array, then the application has access to all channels and can query as necessary with suitable iterators


channel.sequential


The API SHALL be able to provide the webapps with the functions of getting the previous channel and next channel (channel up and down)


The current TVSource.getChannels()<http://w3c.github.io/tvapi/spec/#widl-TVSource-getChannels-Promise-sequence-TVChannel> API provides a sequence of TVChannel<http://w3c.github.io/tvapi/spec/#idl-def-TVChannel> objects. This could be assumed to be “sequential” so that TVChannel[i+1] is the ‘next channel’ from TVChannel[i]


channel.tracks


The API SHALL be able to enable the webapps to switch the video/audio/text tracks of a channel.


Q: When the currentChannel is played though the TVSource to MediaStream, are all tracks from the source (video, all audio, all info/subtitle) given? The MediaStream<http://www.w3.org/TR/mediacapture-streams/> specification only suggests a microphone (audio) and camera (video) track, TVSource would need some API to map received transport stream components onto these (OIPF DAE does this through the selectCompoent/unSelectComponent methods<http://www.oipf.tv/web-spec/volume5.html#extensions-for-playback-of-selected-media-components> for the video/broadcast object)


program.data.audio


For audio: such as language supported, codec used, etc.


Q: Requirements mapping document says the requirement is satisfied by the getAudioLanguages function, but this is only one part of the requirement. DO we need to cover “codec used” here?


program.data.video


For video stream: such as quality, codec used, etc.


See the OIPF DAE specification for information on how various properties/attributes are populated for AVComponent<http://www.oipf.tv/web-spec/volume5.html#mapping-apis-to-content-formats-avcomponent>s, Channel<http://www.oipf.tv/web-spec/volume5.html#mapping-apis-to-content-formats-channel>s, Program<http://www.oipf.tv/web-spec/volume5.html#programme-scheduled-recording-recording-and-download>s (including recorded programs)


program.data.detail


Other detailed information of the channel/program with TV stream.


Q: Can anyone comment on what this additional channel/program information is and how it would be delivered to the receiving terminal? Is there a specific data need or is it just “curiosity”?
You could “JSONify” eberything in the TS, but it is probably not needed.


recording.series


The API SHALL be able to enable the webapps to record series-linked programs.


For the API to implement series recording, it would need to be configured with direct access to a program metadata source.

It may be better to (hopefully) have the App run every 5-7 days, do any program metadata query and schedule individual recordings based on those results.


recording.parental


The API SHALL be able to apply parental controls to playback of recorded programmes.


Unsure where a recorded program is “saved” and what mechanism is used to play it back to the user.. Once the recording API is defined we may be able to do this. That API will need to ensure that the file of the recorded program is not “offloaded” from the receiver and that it is only played back though a TVSource that represents file playback!


parental


The API SHALL be able to provide the webapps with the information whether or not a channel/program is protected and only accessible by a certain group of users, e.g. age-based user groups.


Normally the opposite applies, the webapp sets a “filter” on what content should be allowed for presentation.



An API could be added to retrieve the currentParentalRatings() from a TVChannel<http://w3c.github.io/tvapi/spec/#idl-def-TVChannel>. If such is included, it is probably just an array of strings or comma-seperated list of values.


parental.channel


The API SHALL be able to enable the webapps to lock and unlock the protected channels/programs.


The proposal make for parental control implementation in ACTION-39 certainly covers this, however it only applies “system wide” not on a per object level.


cas*





Q: Is Sung Hei looking at this area?









-----Original Message-----
From: TV Control API Community Group Issue Tracker [mailto:sysbot+tracker@w3.org]
Sent: Tuesday, August 04, 2015 9:50 AM
To: public-tvapi@w3.org<mailto:public-tvapi@w3.org>
Subject: tvapi-ACTION-40: Look at existing requirement gaps for channel and programme data



tvapi-ACTION-40: Look at existing requirement gaps for channel and programme data



http://www.w3.org/community/tvapi/track/actions/40




Assigned to: Paul Higgs