- From: Yves Lafon <ylafon@w3.org>
- Date: Tue, 12 Jun 2012 07:55:14 -0400 (EDT)
- To: Larry Masinter <masinter@adobe.com>
- cc: Robin Berjon <robin@berjon.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "www-tag@w3.org" <www-tag@w3.org>
On Fri, 8 Jun 2012, Larry Masinter wrote:
>> ... 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.
I'm not sure that the scope of AWWW is at this level of detail.
> The TAG has taken on one of the elements (local vs. remote storage), but
> I don't think we have an overall framework.
And local storage can be seen as "state stored on the client", which is no
different from cookies for example, just APIs and implementation details,
but overall it's only that.
> I know of no working group chartered to put together such a framework.
> It would be an extension to AWWW.
>
> Larry
>
>
>
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Tuesday, 12 June 2012 12:12:19 UTC