- From: Giuseppe Pascale <giuseppep@opera.com>
- Date: Mon, 03 Oct 2011 12:14:53 +0200
- To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Hi all, in order to finalize the requirement document, I would like to ask you feedback about the following two potential changes. If no objection is raised I'll go ahead and apply them: * Gap Analysis: - add a section "Gap Analysis" to "1.9 Categorization of Requirements and next steps", after "1.9.1 Requirement Categorization" - add the following text to such a section: "==Gaps== A close analysis and discussion of the use-cases and requirements described in this document, lead the group to conclude that the **major** gap in the Open Web platform is the lack of means for an application to discover services and applications available on the home network. Filling such a gap will probably allow the coverage of most (if not all) requirements listed in this documents. 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 my 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. The discussion will have to be deferred to the point in time when such discovery implementation will be available." * Requirements about content player discovery/control Some concerns were raised that the following requirements can be actually considered as part of the equivalent generic service advertisement/control/discovery: - 1.6.2.4 Content Players Discovery, - 1.6.3.1 Control of content players - 1.6.3.2 Control of content recorders What should I do with them? Should I remove them from our document? I'm personally fine removing them. * Content Discovery/advertisement Some concerns were raised that also content discovery/advertisement may be included in the generic service discovery/advertisement. The requirements are: - 1.6.2.3 Content Discovery - 1.6.2.5 Content Advertisement What should I do with them? Keep them or remove? I think is still valuable to keep them, since is an important requirement that could actually require something more then generic service discovery/advertisement /g -- Giuseppe Pascale TV & Connected Devices Opera Software
Received on Monday, 3 October 2011 10:15:22 UTC