W3C home > Mailing lists > Public > public-web-and-tv@w3.org > October 2011

RE: [HOME_NETWORK_TF] Identified gaps (was Re: [HOME_NETWORK_TF] Finalizing the HNTF req doc)

From: <david.corvoysier@orange.com>
Date: Mon, 10 Oct 2011 13:56:41 +0200
Message-ID: <E6AA070839B987489960B202AD80E18D019D925A@ftrdmel0.rd.francetelecom.fr>
To: <public-web-and-tv@w3.org>
 
Hi,

I am not sure we need to go into the "advertisement as a service" complexity, especially at the requirement/gap analysis level.
Conversely, we need to explicitly state that we require discovered services to be exposed to the application as raw URLs, otherwise we will not be able to use UPnP/Zeroconf from the JS.
For instance, Safari already supports airplay, but it is only available through the video player standard controls (although the feature can be toggled on/off from javascript).  

As a side note, there seems to be a few typos in the following sentence:

"Is not clear though (lucking implementations of this) if this approach will be enough flexible and efficient."
Did you mean: "It is not clear though (lacking implementations of this) if this approach will be enough flexible and efficient" ?

David

-----Message d'origine-----
De : public-web-and-tv-request@w3.org [mailto:public-web-and-tv-request@w3.org] De la part de Giuseppe Pascale
Envoyé : mardi 4 octobre 2011 11:57
À : public-web-and-tv@w3.org
Objet : [HOME_NETWORK_TF] Identified gaps (was Re: [HOME_NETWORK_TF] Finalizing the HNTF req doc)

I've added a new section based on the F2F discussion and the feedbacks I got on this list.

Please let me know if you have any other comment:
http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Requirements#Identified_Gaps


/g

On Mon, 03 Oct 2011 17:32:53 +0200, Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr> wrote:

> On 3/10/11 15:35 , Giuseppe Pascale wrote:
>>
>> [[
>> Some concerns were raised if the discovery alone is enough to address 
>> advertisements requirements especially for support of existing 
>> protocols such as UPnP. In fact, advertisements itself could be 
>> implemented as a service so that applications can discover it and 
>> then register to be advertised on the network. Such a service may be 
>> provided by the UA itself (i.e. the functionality is provided by the 
>> UA but exposed as a service). Is not clear though (lucking 
>> implementations of this) if this approach will be enough flexible and efficient.
>>
>> ****Furthermore to have an interoperable solution, a common 
>> advertising service would have to be standardized or JS binding to 
>> already in use advertising services/protocols would have to be 
>> provided.***
>>
>> The discussion will have to be deferred to the point in time when a 
>> UA supporting discovery will be available.
>> ]]
> JCD: Yes, that works. Thanks.
> Best regards
> JC
>


--
Giuseppe Pascale
TV & Connected Devices
Opera Software
Received on Monday, 10 October 2011 21:24:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 October 2011 21:24:31 GMT