- From: Vickers, Mark <Mark_Vickers@cable.comcast.com>
- Date: Thu, 29 Sep 2011 16:14:07 +0000
- To: Giuseppe Pascale <giuseppep@opera.com>
- CC: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
I think one gap would be a simpler message, if it can also be used for advertising a service. We have a stronger position on discover going into TPAC: - multiple apps showing the gap - a group with discovery charter (DAP) - proposals for new API posted to DAP site - prototype implementations of the proposed spec Based on this extensive work, I personally understand the specifics of the discovery gap more than I do the advertisement gap. Thanks, mav On Sep 29, 2011, at 5:04 AM, Giuseppe Pascale wrote: > Hi all, > there was an action point on me to try and finalize the requirement document based on the discussion we had during our F2F. > Unfortunately I'm still working on it, but I'll inform you on this list once this is done and ready for final review. > > While I work on it, I would like to list here what I expect to write, so you can let me know if you have comments: > * Apply all changes approved during the F2F (from Russell) > ** Russell, I know there are few pending issues from you, I'll send you a separate email about those. > * Leave all requirements/use cases as they are now (above changes a part) > * Add a new section about "Gaps" where we outline that we find 2 major gaps: discovery and advertisement. And explain that filling such gaps may be enough to cover all requirements. > ** Actually, I've been considering going down to ONE gap: discovery. Once you have discovery, you may implement advertisement as a service (at least to start with). What do people think? > > > comment are welcome > > > /g > > -- > Giuseppe Pascale > TV & Connected Devices > Opera Software >
Received on Thursday, 29 September 2011 16:15:15 UTC