- From: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
- Date: Tue, 07 Jun 2011 11:28:23 +0200
- To: Giuseppe Pascale <giuseppep@opera.com>
- CC: Russell Berkoff <r.berkoff@sisa.samsung.com>, Matt Hammond <matt.hammond@rd.bbc.co.uk>, public-web-and-tv@w3.org
On 3/6/11 17:14 , Giuseppe Pascale wrote: > ** Service Distribution (ISSUE-8) > This looks fine to me, even though as you say the only additional > requirement of the use case (compared to the others) is to be able to > push services rather then discover services. > Probably good to extend with few more words the "Need/justification:" > section of the template JCD: I have added this text: As there are more devices in the home, some generic and some task-specific, and with varying capabilities (including different UI methods), there is a growing need to spread an application across different devices to achieve service distribution. But the service usually "enters" the home network through one particular device. The service running entirely on the initial device, as part of other use cases, can discover its environment and determine that other devices could meaningfully contribute to the quality of experience. From then on, the service needs to send part of "itself" to other devices. Hence this use case. Best regards JC -- JC Dufourd Directeur d'Etudes/Professor Groupe Multimedia/Multimedia Group Traitement du Signal et Images/Signal and Image Processing Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144
Received on Tuesday, 7 June 2011 09:28:46 UTC