The specs concentrate on mandatory system standards and delivery of TV and video, and are intended for system architects, but lack detail on just how Canvas will implement an “app store” they refer to. There is also no mention of how Canvas will support conditional-access payment systems.

But this is a first draft. Here are the key points we are picking out… (see the BBC’s earlier initial and fuller proposals).

Standards and languages

Canvas is looking at supporting HTML4 and “a subset of HTML5 (draft), including Web Forms, Web Storage and <audio>, <video> and <canvas>” HTML tags.

It’s considering supporting Flash Player 10.

“Devices shall be built using the Linux operating system with either glibc or uClibc” (libraries of the C language).

Apps and widgets?

There will be a “Web Apps” section, available via a remote control key.

Canvas will have a Core UI consisting of its main menu and EPG, plus “Content Provider Applications: This type of application is produced by Content Providers and can take the form of VOD portals, web-style apps, widget overlays (as supported by the relevant presentation technology) etc. A successful connected television platform will have many such applications.”

“Content Providers applications are the responsibility of content providers to provide. Such applications will be launched from the Core UI.  This could be as a result of direct selection of the Content Provider application itself, e.g. listed within an “app store”.  Or it could as a result of the selection of an item of AV content (e.g. from some centralised “content browse” capability) that is dependent on the Content Provider application for its successful presentation.”

There will be developer APIs for building applications.

“Applications can potentially be authored in any language supported by Application Players e.g. MHEF, HTML/JavaScript, ActionScript. They are distributed in a processor independent form (e.g. script or byte code).”

Personalisation

Viewers will see Recommendations based on “some combination of explicit editorial recommendations provided by content providers, usage tracking data obtained anonymously from the service device and specific recommendations addressed from one end user to another.”

Some devices may support multiple viewer profiles within a household.

Devices will automatically record shows viewers are deemed most likely to watch.

Monitoring

“The migration to a connected television environment greatly increases the complexity” of gathering audience metrics because “the same item of content can be available from more than one source” (ie. Channel 4, 4oD and YouTube).

“Given the huge increase in the volume of content on offer – enabled by IP delivery - knowing how content is discovered will enable crucial optimisation of user interfaces.

“Applications will become an increasingly used content format and knowing how they are used will allow for the refinement of existing and inform the development of new services.

So “the device shall provide a mechanism for connection to an audience-monitoring unit provided by BARB” (via USB)” - but only for homes which are already BARB panelists.

“To satisfy the needs of this evolving environment a more fully featured and adaptable usage measurement capability will be required” (a BARB-beater?).

Content providers will also get to see logs of Canvas hits to their websites, via a User Collection Agent, but viewers can opt out.

ISPs will get to remotely monitor Canvas devices to identify faults early.

User interface customisation

“The Core UI application is the responsibility of the UI Provider (ed: that’s the Canvas JV itself) to supply.  This shall be implemented such that device manufacturers and ISPs can configure aspects of the Core UI so as to customise its operation. 

“The specific detail of such customisation is beyond the scope of the this document but possible examples include: an ISP specific menu item within the Core UI that launches a ISP application providing customer help; inclusion of device manufacturer branding on screens within the Core UI.”

Virgin Media (NSDQ: VMED) has complained that a bolt-on menu does not offer enough customisation of the Core UI; otherwise, it would join Canvas.