RE: HbbTV 2.0 Specification Announcement

Hi Mark,

Broadcast Independent Applications are Internet delivered HTML Applications that have access to features specified in HbbTV spec but not related to any broadcast channel or other broadcast data. Broadcast Independent Applications are identified either by the URL of the HTML document (e.g. http://www.example.com/whizzo-app.html ) or the URL of the AIT XML Document (e.g. http://www.example.com/whizzo-ait.xml) as you mentioned in your example below. There are different ways to start a Broadcast independent Application (see section 6.2.2.6.1 of the HbbTV 2.0 Spec for more details). To launch from companion screen  the AIT XML must be sent in the Body . The elements <mhp:orgId> and <mhp:appId> are mandatory (Valid organization Ids are registered on dvbservices.com [1]). To launch the Application only the elements  <mhp:URLBase> and  <mhp:applicationLocation> are relevant. But the TV manufacture may Check first if <mhp:orgId> and <mhp:appId> are valid are not. If they are not valid, the Application may not be started. In our case in Presentation API, in addition to the presentationUrl, we need to know the values of mhp:orgId and mhp:appId in order to construct the AIT XML.  I hope this answers your question.
I don´t know why Launching Broadcast Independent Applications from Companion Screens using only the URL of the HTML document is no supported ☹.

Louay

[1]: http://www.dvbservices.com/identifiers/mhp_organisation_id


From: Mark Scott [mailto:markdavidscott@google.com]
Sent: Mittwoch, 25. Februar 2015 09:20
To: Bassbouss, Louay
Cc: mark a. foltz; public-secondscreen@w3.org; public-webscreens@w3c.org
Subject: Re: HbbTV 2.0 Specification Announcement

Hey Louay,

Can you clarify the scope of broadcast independent applications?  From the example in the spec, it seemed like the descriptors for these broadcast independent apps simply referred to an URL, but perhaps I was misreading this.  In particular, 14.6.2 for launching such apps used this example:

<mhp:ServiceDiscovery xmlns:mhp="urn:dvb:mhp:2009"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <mhp:ApplicationDiscovery DomainName="example.com<http://example.com>">
 <mhp:ApplicationList>
 <mhp:Application>
 <mhp:appName Language="eng">Whizzo Play Along Quiz</mhp:appName>
 <mhp:applicationIdentifier>
 <mhp:orgId>123</mhp:orgId>
 <mhp:appId>456</mhp:appId>
 </mhp:applicationIdentifier>
 <mhp:applicationDescriptor>
 <mhp:type>
 <mhp:OtherApp>application/vnd.hbbtv.xhtml+xml</mhp:OtherApp>
 </mhp:type>
 <mhp:controlCode>AUTOSTART</mhp:controlCode>
 <mhp:visibility>VISIBLE_ALL</mhp:visibility>
 <mhp:serviceBound>false</mhp:serviceBound>
 <mhp:priority>1</mhp:priority>
 <mhp:version>01</mhp:version>
 <mhp:mhpVersion>
 <mhp:profile>0</mhp:profile>
 <mhp:versionMajor>1</mhp:versionMajor>
 <mhp:versionMinor>3</mhp:versionMinor>
 <mhp:versionMicro>1</mhp:versionMicro>
 </mhp:mhpVersion>
 </mhp:applicationDescriptor>
 <mhp:applicationTransport xsi:type="mhp:HTTPTransportType">
 <mhp:URLBase>http://www.example.com/whizzo-app.html</mhp:URLBase>
 </mhp:applicationTransport>
 <mhp:applicationLocation>?launch=from-cs</mhp:applicationLocation>
 </mhp:Application>
 </mhp:ApplicationList>
 </mhp:ApplicationDiscovery>

I'd assumed, perhaps incorrectly, that the base URL above defined the app, but perhaps it is the appID (456) that refers to some pre-defined app ID?

Mark.

On Tue, Feb 24, 2015 at 11:29 PM, Bassbouss, Louay <louay.bassbouss@fokus.fraunhofer.de<mailto:louay.bassbouss@fokus.fraunhofer.de>> wrote:
Hi Mark,

I followed the HbbTV activities in last years since we are HbbTV member. To make it more clear the HbbTV 2.0 supports launch HbbTV Brodcast independent applications on the TV and not any kind of web applications ( e.g. by using presentation URL). To support presentation API on TVs many HbbTV 2.0 components could be reused.

Louay

On 24 Feb 2015, at 22:19, mark a. foltz <mfoltz@google.com<mailto:mfoltz@google.com>> wrote:
Second-screen WG (& Webscreens CG),

I wanted to make you aware of a recent announcement [1] by the HbbTV 2.0 consortium of a proposed specification for discovery and control of Smart TVs [2] that would allow "companion devices" (e.g., browsers) to launch a Web application on the TV using DIAL [3].

The relevant discussion can be found in Section 14 of the specification, "Companion Screens," which I have yet to digest fully.

If this specification is adopted by manufacturers, it would mean that a large number of endpoints would become compatible in principle with many aspects of the Presentation API.  We should keep this in mind as we develop the Presentation API specification.

[1] http://www.digitaltveurope.net/320392/hbbtv-2-0-specification-announced/

[2] http://www.hbbtv.org/pages/about_hbbtv/HbbTV_specification_2_0.pdf

[3] http://www.dial-multiscreen.org/


m.