- From: Larry Masinter <masinter@adobe.com>
- Date: Fri, 8 Jun 2012 13:44:53 -0700
- To: Robin Berjon <robin@berjon.com>
- CC: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "www-tag@w3.org" <www-tag@w3.org>
> ... What would the TAG be writing about? > What problem would we be addressing that isn't already on the menu for a working group? I'd like Hannes to elaborate what questions he'd like answered, but my take is: In the best of worlds, working groups focus on specific technology choices and specifications that can be implemented and deployed, and the role of the TAG is to document the overall architectural framework into which the technology choices fit. AWWW doesn't talk about native applications and the relationships and tradeoffs for security, privacy, monetization, reliability, offline operation, of native apps, web apps, and widgets. The TAG has taken on one of the elements (local vs. remote storage), but I don't think we have an overall framework. I know of no working group chartered to put together such a framework. It would be an extension to AWWW. Larry
Received on Friday, 8 June 2012 20:45:25 UTC