Common questions relating to the framework.
Answer: TV Application Layer
Answer: TAL is for HTML technology based devices. It does not support Flash or MHEG.
Answer: TAL was created by the BBC to build TV Applications.
Answer: TAL is available to everyone under the terms of the Apache V2.0 open source licence.
Answer: the BBC has adopted a dual licensing approach and can make available TAL under a separate proprietary licence agreement. Please contact us for details of these terms.
Answer: The biggest technical reason for making TAL available as an open source project is so that it can be picked up and contributed to by others (manufacturers, content providers, 3rd parties), helping to standardise the the way TV Applications are made, and benefitting everyone.
Answer: There is a short tutorial that we found quite useful.
Answer: We looked at the wide range of licences and found that Apache v2.0 best met our requirements. Specifically it encourages others to contribute, whilst not restricting its use in commercial products. It’s also a well recognised licence type. For more details about the Apache 2.0 licence see the Open Source Initative
Answer: Yes. This is the live repository that the BBC uses to host its code and it build its own TV Applications with. It is not a copy or a mirror.
Answer: TAL will work on most HTML-based Connected TV devices and it’s structured in such a way that it’s relatively easy to add support for a device that isn’t already supported.
Answer: TAL will work on Samsung devices (2010 onwards), Panasonic (2011 onwards), Sony (2011 onwards), Toshiba (2011 onwards), LG (2012 onwards) and a whole range of others. Please see the config folder
Answer: There are two likely answers to this. The first is that TAL doesn’t work on that device
(either the BBC has not seen it yet or when we did, there was a problem getting TAL to run on it).
Secondly, it could be that the manufacturer hasn’t granted permission for the file to be hosted here.
Answer: TAL is technically able to run on most Sony devices from 2011 onwards, please contact them for more detailed information.
Answer: TAL is technically able to run on most Samsung devices from 2010 onwards, please go to http://www.samsungdforum.com/ for more detailed information.
Answer: Using one of the existing device configuration files as a guide:
Answer: We ask all manufacturers for permission to share the device configuration file specific to their device. If you haven’t completed the waiver document and want to then please fill out and return the waiver
Answer: Internally the BBC has a database that matches device-browser user-agents to device-configuration files (BRAND-MODEL-default.json), but that is not part of what is being shared here. See the SampleApplication for an alternative approach to doing it. The sample application works by specifying the device config file as a URL parameter, but its up to you how you do it.
Answer: The BBC uses its own internal database, which is based on the WURFL project.
Answer: See the device configuration page for specific details.
Answer: To get a reference to the device, include RuntimeContext in your require.js dependencies (
"antie/runtimecontext"), then in your code get a reference with
var device = RuntimeContext.getDevice();.
Answer: Currently it doesn’t, but the TAL project has talked to several DRM providers who are interested in looking at integrating their solutions with TAL.
Answer: TAL has been built pragmatically. We’ve followed standards where possible and tried to encourage manufacturers to do the same, but where its not possible for some reason, we may solve the problem creatively. We provide implementations of abstractions complying with industry standards (W3C, HbbTV, DTG). For example, TAL abstracts the W3C and CE-HTML specifications which achieve the common goal of media playback.
Answer: Yes, we’ve included a default configuration file in the TAL project code.
Answer: You will see ANTIE throughout the code. It’s the just the original code name for the project, before it became TAL.
Answer: Please see the contributing page to see how to get in touch.