This Web API has to cover the following user cases: 1. This API is able to let the user configure the current channel list. 2. This API is able to let the users create their own favourite channel lists either by explicit selections or by filtering conditions. 3. The channel lists can be shared to other apps including arbitrary third-party apps.
Although the OIPF spec defines lots of APIs for the web apps to access or configure the TV channel lists like: - readonly ChannelList channelList - readonly FavouriteListCollection favouriteLists - readonly FavouriteList currentFavouriteList - onChannelListUpdate() - ChannelList createFilteredList( Boolean blocked, Boolean favourite, Boolean hidden, String favouriteListID ) - ChannelList createChannelList( String bdr ) - ... etc. From Mozilla's point of view, this issue can be reduced to a DataStore API  problem. That is, we can define a data store named "tv-channel-lists" (naming can be discussed) which is aimed for collecting all the app-customized channel lists. This data store can be just owned by the System App or by the certified TV App. For arbitrary apps that want to access the channel lists, the rest is nothing but a permission issue: only the apps with the write-permission can modify the channel lists and only the app with the read-permission can read the channel lists. In short, we think it's not worth implementing a specific Web API for configuring the TV channel lists, especially when the data can be totally maintained on the app side (i.e., we don't really benefit from implementing the logic on the platform side). To share the channel-list data among apps, we can leverage the existing DataStore API to deal with the synchronization issue.  https://wiki.mozilla.org/WebAPI/DataStore
You need to log in before you can comment on or make changes to this bug.