Document Schedule

Project Canvas Document Schedule: First published release Overview: The Project Canvas Document Schedule outlines when Project Canvas will be releasing key information to industry including technical documents, requests for expressions of interest from ISPs, content providers and retailers and operational guidelines, including brand guidelines and the User Interface Policy. Project Canvas believes that through this industry engagement, it can help to ensure that industry participants including device manufacturers, content and service providers; and retailers can participate in the Canvas environment. Further updates to the schedule will be published on the Project Canvas web site. Document Schedule:

Date	Published to	Document Name	Document Description
May 2010	DTG	Consumer Device Platform Specification	This document defines a common low-level “platform” for all Canvas consumer devices, which in addition to the obvious specification of required connectors, remote control buttons etc. seeks to: Ensure that a minimum level of consumer experience can be achieved.This involves the specification of hardware requirements that extend to the main SoC/processor, such as hardware AV codec support, hardware decryption support and hardware graphics acceleration. This is to allow a range of different SoCs to be used whilst still achieving the desired objective. This also involves the specification of how such hardware capability can be exposed to higher-level software in a consistent, compliant manner. Increase the inherent compliance of consumer devices through use of common software components.This relates to a formalisation of strong, existing industry trends around the use of common open source software components, in line with the current or intended approach of many manufacturers.
May 2010	DTG	Broadcast Content Delivery Specification	This document defines the specification for delivery of broadcast content. The initial version of this document relates to DTT broadcast services in the UK. This includes support for SD and HD services, support for DVR functionality and support for broadcast interactive (red button) services via the UK Profile of MHEG. Given that these features are already well-defined by the DTG D-Book, which can simply be referenced, the main purpose of the Broadcast Content Delivery Specification is to: Profile existing functionality that needs to be modified in the context of the addition of IP content delivery. Specify additional functionality required to make the integration of broadcast and IP as effective as possible. From its outset Project Canvas has sought to minimise the extent of any such extensions. This is in part to minimise the need for re-engineering of broadcast infrastructure and hence to avoid disruption to existing broadcast services; it is also in part to minimise the extent of any modifications to software components providing broadcast support within consumer devices. The minor nature of additional functionality identified to date should serve to reassure industry as to this intent.
May 2010	DTG	Consumer Device Software Management Specification	This document defines the mechanism to enable (i) the device manufacturer, (ii) the proposed Canvas JV and (iii) the relevant broadband provider (ISP) to set configuration parameters for the Canvas consumer device. The document also describes the mechanism for upgrading the software on a Canvas consumer device. This will be in two parts: Upgrade of the core device image. This will be the responsibility of the device manufacturer and may be achieved via existing broadcast-based arrangements and IP using privately defined mechanisms. Upgrade of applications and services managed by the proposed Canvas JV, such as the Top-Level UI, which are common to all Canvas consumer devices.
May 2010	DTG	IP Content Delivery Specification	This document defines the ways in which content can be acquired and consumed over IP. This includes specification of the core network stack and its configuration, which will be underpinned by a set of technology standards, many published by the IETF. The document also provides detailed specification of a set of A/V media delivery mechanisms to support four key use cases for A/V media delivery: Streaming of non-live content (video-on-demand). Streaming of live content. Download of programmes to local storage. Close integration of A/V content and user interaction. Support for these use cases will be based on the use of: Video and audio codecs with hardware decode support in the Canvas consumer device. MPEG-2 TS and MP4 container formats. Adaptive and multicast technology.
May 2010	DTG	Metadata Model	This document describes the overall model for the interchange and exploitation of metadata over both broadcast and IP delivery paths. This will include the use of: Descriptive metadata, to attract users to media content and encourage them to consume it. Publication metadata, to allow publication instances to be located and consumed. The Metadata Model covers: Existing metadata delivered over broadcast, e.g. DVB-T. Metadata used to power third party (content provider) applications. Managed “platform” metadata, used to power the Top-Level UI and other client services managed by the proposed Canvas JV. In doing this it will identify which metadata interfaces will be based on existing standards, which will require standardisation and which will be managed by an individual party.
June 2010	DTG	Consumer Device Software Architecture	This document defines the Canvas consumer device software architecture that will address challenges relating to integration, evolution and compliance. This includes the need to: Bring together broadcast and IP delivery technologies so as to ensure effective co-existence. Manage the presentation of and interaction with multiple concurrent runtime applications. Surface the configuration and controls for key elements of the software stack to enable “in-field” performance tuning. Provide a means to apply security policies to client services and third party applications. Enable consistent instrumentation of usage capture and diagnostics functionality. This is not about mandating a single software stack (“middleware”) for all consumer devices; rather, it is about an integration framework underpinned by a number of common enabling technologies. This will make it easier to both integrate common third party components and will allow common compliance testing material to be applied throughout (and consequently earlier) in the device development lifecycle.
June 2010	DTG	Usage Measurement Model	This document describes the overall model for the collection and export of usage measurement data from the Canvas consumer device. Two export targets for usage data are already envisaged: Backhaul over IP to the proposed Canvas JV. A BARB Panel Meter connected to the Canvas consumer device. As the usage data required by each of these targets is different and may need to change over time it will be necessary to be able to evolve what data is exported. And in the case of backhaul over IP, to be able to limit the extent of any server-side infrastructure it will be necessary to be able to apply sampling controls. The Usage Measurement Model also defines how this “in-field” evolution will be supported.
July 2010	Project Canvas website	Content Protection Paper	The content protection strategy is designed to enable Canvas to support the widest possible range of content types for internet-connected TV audiences. The document sets out a range of content protection options to give individual content providers flexibility over the level of protection they wish to adopt, and consumers the widest range of content. As an open platform, providers can choose to make content available with no protection at all, or adopt transport encryption, file encryption, device authentication, or digital rights management (DRM). Conditional Access upgrade will also be possible for those who require it.
July 2010	DTG	Content Acquisition & Management Specification	Canvas aims to make content acquisition functions in the consumer device as autonomous as possible due to their mission critical nature. This will also enable maximum re-use of existing, tried-and-tested code for both programme acquisition from broadcast (as found in existing DVR products) and media asset download over IP. In a standard (non-IP) DVR device the programme acquisition from broadcast function can operate on the assumption that it controls the only way to acquire content onto the device. Hence all of the decision making logic (or “business rules”) can be restricted to this function alone and internalised. The same is true of a media asset download over IP function in an IP only device. However, when the two acquisition functions are both present the business rules needs to span both functions. For example, if the DVR fails to acquire a particular broadcast instance it may be better to initiate an IP download than wait to acquire a repeat transmission several days later. This means the business rules can no longer be internalised to the individual functions. The Content Acquisition & Management Specification defines how such business rules for content acquisition will be defined and applied. As the required acquisition strategy is certain to change over time, due to increased understanding of audience behaviour and changing commercial models, the “rules” underpinning this will need to evolve in the field. The Content Acquisition & Management Specification also defines how this “in-field” evolution will be supported.
July 2010	DTG	User Interface Management Specification	This document defines how a Canvas consumer device will support more than one Presentation Engine technology and hence different types of applications. It also describes how a Canvas consumer device will support multiple concurrent applications, of the same or different types. This definition falls into 4 main areas: Lifecycle management for individual applications. Handling and routing of user input to active applications. Composition of the rendered form of active applications into a unified presentation to the user. Management of access to shared consumer device hardware resources, such as AV decode and graphics acceleration. Lifecycle management will need to reflect supported user interaction patterns; e.g. how applications launch each other, how focus is moved between applications, and how applications persist across channel changes. As the supported user interaction patterns are certain to change over time, due to increased understanding of audience behaviour and changing commercial models, the “rules” underpinning lifecycle management will need to evolve in the field. Furthermore, the composition of concurrent applications will need to operate within an “envelope” of the capability of the underlying consumer device hardware; e.g. the number of graphics planes, available hardware acceleration, and memory bandwidth limits. This will require composition rules to be “tuned” to stay within practical limits. The User Interface Management Specification defines how this “in-field” evolution will be supported.
July 2010	DTG	Consumer Device Remote Management & Diagnostics	This document defines the way that remote diagnostics and monitoring shall be implemented by a device that supports such functionality.
August 2010	DTG	IP Content Delivery: Content Protection	This document defines the way in which rights-sensitive A/V content can be protected and managed both in distribution and whilst it exists in the consumer device. The document defines a range of content protection mechanisms that will give content providers choice about what they employ; i.e. to only need to use something that is sufficient given the nature of the content being delivered.
August 2010	DTG	Consumer Device Requirements Specification	This document will define the functional requirements that need to be provided by a Canvas consumer device. As such it would provide a definitive statement of what needs to be implemented. Over time it will evolve to define the functional requirements for more than one variant of Canvas consumer device, e.g. DVR, non-DVR, IP only, IDTV variants. The document will reference and build on equivalent text in the current DTG D-Book (“Chapter 22”) as well as the other documents in the Canvas specification set. Subject to the outcome of the DTG’s Connected TV activity parts of this document may be re-factored to reference future versions of the DTG D-Book.
August 2010	DTG	Presentation Engine Profile Specification	This document defines the presentation technology available to content developers beyond the MHEG technology already available for “red button” services.
August 2010	DTG	Consumer Device User Interface Model	The user experience offered by a Canvas consumer device will be provided by a combination of: A top-level UI managed by the proposed Canvas JV. A device-specific UI provided by the manufacturer. A large number of third-party applications in the form of portals, services and web apps. This document describes the model for how these different elements will be integrated in a seamless manner. This specification is likely to change over time in line with evolving operational requirements.
September 2010	Project Canvas website	Expressions of Interest: Affiliate ISPs	This document is a short request for any ISP interested in becoming a Canvas affiliate to contact the venture to begin discussions.
September 2010	Project Canvas website	Expressions of Interest: Third party content providers	This document is a short request for any content provider interested in providing content onto Canvas to contact the venture to begin discussions.
September 2010	Project Canvas website	Expressions of Interest: Retailers	This document is a short request for any UK retailers (High street and online) interested in supporting and promoting the Canvas brand and marketing activity to contact the venture to begin discussions.
October 2010	Project Canvas website	User Interface Style Guide & Interaction principles	Style guide for all partners containing the Canvas fonts, template and user interface-specific technical specifications.
October 2010	Project Canvas website	Affiliate ISP Guidelines	This document defines the standards and guidelines that an internet service provider (ISP) is expected to comply with in order to become an affiliate of the Canvas platform.
October 2010	Project Canvas website	User Interface Policy (Business Rules)	This document defines the business rules for 3^rd party branding to appear within the Canvas user interface.
October 2010	Project Canvas website	Trademark Licence Policy	The Trademark Licence Policy sets out: The principles of the ventures approach. What the venture will and will not do or provide in relation to this topic. Terms of agreement between the venture and any 3rd party in relation to this topic.
October 2010	Project Canvas website	Device Compliance Rules and Test Plan	This document describes the testing and compliance elements required to achieve Canvas accreditation (Digital tick, Canvas tick, DRM etc.).
December 2010	Project Canvas website	EPG Policy (including editorial standards)	This business policy sets out: Principles of the ventures approach. What the venture will and will not do or provide in relation to this topic. Terms of agreement between the venture and any 3rd party in relation to this topic.
February 2011	Project Canvas website	Portals and Players Guidelines	This document defines the guidelines that a content provider will need to comply with when supplying content to be displayed on the Canvas platform. It sets out the technical standards that a provider needs to comply with (such as encoding standards, and required metadata), as well as any design guidelines that must be adhered to.
February 2011	Project Canvas website	Developer API Reference	This document will detail the API’s available to developers producing content for Canvas.
February 2011	Project Canvas website	Developing Applications	This document will provide detailed information on how to develop applications for Canvas.
March 2011	Project Canvas website	Brand in-store retail implementation	This document will incorporate the Brand Guidelines and will reference the Trade Mark Licence agreement, as well as provide specific requirements for retail in-store marketing and support of the Canvas Brand.