- From: Giuseppe Pascale <giuseppep@opera.com>
- Date: Mon, 22 Aug 2011 16:44:21 +0200
- To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>, "Matt Hammond" <matt.hammond@rd.bbc.co.uk>
On Sun, 21 Aug 2011 20:20:43 +0200, Matt Hammond <matt.hammond@rd.bbc.co.uk> wrote: > Hi all, > > Apologies for this being a little later than I originally intended: as I > mentioned in last week's conf call, I have a comment regarding the > "Application Communication" requirement. > > Would it be helpful to clarify that this requirement is specifically > intended to enable direct communication between applications? This would > be to distinguish it from an implementation that (for example) sent all > communications through a cloud based relay or proxying service? > > For example: "Conforming specifications should provide a means for > applications to exchange messages directly via the home network with other > applications running on a different user agent in the home network." > Hi Matt, thanks for raising this in writing. I agree that several (all?) of the use cases we have discussed require (preferably) a direct communication. I think this is pretty uncontroversial and could add it right away to the requirement document. Some of the use cases could actually be covered by an indirect communication mechanism as well, so probably also that would be in scope. On other end such a mechanism may either not need (additional) standardization or fall back to the a different discussion about which services could be standardized. So in short I'm fine to re-word the requirement as you suggested if nobody objects. /g > regards > > > > Matt -- Giuseppe Pascale TV & Connected Devices Opera Software - Sweden
Received on Monday, 22 August 2011 14:45:03 UTC