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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
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 3rd party branding to appear within the Canvas user interface. |
October 2010 |
Project Canvas website |
Trademark Licence Policy |
The Trademark Licence Policy sets out:
|
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:
|
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. |
You can download the Project Canvas Document Schedule document here
Canvas – Our News
Five comes back to Project Canvas
Date: Sep 24, 2010
“YouView” unveiled as the future of television
Date: Sep 16, 2010
Industry gets behind Project Canvas
Date: Sep 9, 2010
Five comes back to Project Canvas
Date: Aug 24, 2010
Project Canvas partners further engage with device manufacturers
Date: Aug 11, 2010
Canvas in the News
Jeremy Hunt: Project Canvas Is Incredibly Exciting’ | paidContent:UK
Date: Sep 10, 2010
Channel 5 rejoins Project Canvas
Date: Aug 31, 2010
Channel 5 rejoins Project Canvas
Date: Aug 26, 2010
Channel Five back in Project Canvas
Date: Aug 26, 2010
Channel 5 returns to Project Canvas fold – Business News – Independent.co.uk
Date: Aug 26, 2010
@canvasinfo
canvasinfo: Check out the new #YouView website – www.youview.com
Date: Sep 16, 2010
canvasinfo: Join us at @YVTV for all the latest on why #YouView is the future of television
Date: Sep 16, 2010
canvasinfo: No longer Project Canvas. From now on we’re #YouView
Date: Sep 16, 2010
canvasinfo: Hi @ianjamesdavies @ianwareing, we’ll be posting links at 11:30 to all the latest info or email us [email protected] with q’s
Date: Sep 16, 2010
canvasinfo: News on the future of television will be announced at 11.30am
Date: Sep 16, 2010
canvasinfo: Industry gets behind #project canvas with 40 manufacturers expressing strong support to develop Canvas devices http://tinyurl.com/348ldp4
Date: Sep 9, 2010
canvasinfo: Jeremy Hunt: #projectcanvas is ‘Incredibly Exciting’ http://cnt.to/mju > we agree, but canvas strips out the chaos via @paidcontentuk
Date: Sep 9, 2010
canvasinfo: @DocEvil666 thanks for the #ff Doc
Date: Sep 6, 2010
canvasinfo: #ChannelFive rejoins #projectcanvas. Richard Desmond says open #iptv platform will “shape the future of broadcasting” http://is.gd/eAplq
Date: Aug 24, 2010
canvasinfo: #project canvas calls out for expressions of interest from device manufacturers to bring Canvas devices to market http://tinyurl.com/2u9uet8
Date: Aug 11, 2010