W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2008

RE: Request for Comments on Widgets 1.0 Requirements Last Call WD

From: Phillips, Addison <addison@amazon.com>
Date: Thu, 26 Jun 2008 13:58:14 -0700
To: Arthur Barstow <art.barstow@nokia.com>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
CC: Marcos Caceres <m.caceres@qut.edu.au>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013B5E02E7@EX-SEA5-D.ant.amazon.com>
Hi Art,

Thanks for this note. We'd be glad to provide comments. I've place it onto our Homework page and we'll be back in touch with comments (if any) soon.

Best Regards,

Addison

Addison Phillips
Globalization Architect -- Lab126
Chair -- W3C Internationalization Core WG

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: public-i18n-core-request@w3.org [mailto:public-i18n-core-
> request@w3.org] On Behalf Of Arthur Barstow
> Sent: Thursday, June 26, 2008 1:48 PM
> To: public-i18n-core@w3.org
> Cc: Marcos Caceres
> Subject: Request for Comments on Widgets 1.0 Requirements Last Call
> WD
>
>
> Addison, I18N Core WG,
>
> On June 25 the Web Applications WG published a Last Call Working
> Draft of the Widgets 1.0 Requirements document:
>
> [[
> <http://www.w3.org/TR/2008/WD-widgets-reqs-20080625/>
> Abstract: This document lists the design goals and requirements
> that
> a specification would need to address in order to standardize
> various
> aspects of widgets. Widgets are small client-side Web applications
> for displaying and updating remote data, that are packaged in a way
> to allow download and installation on a client machine, mobile
> phone,
> or mobile Internet device. Typical examples of widgets include
> clocks, CPU gauges, sticky notes, battery-life indicators, games,
> and
> those that make use of Web services, like weather forecasters, news
> readers, email checkers, photo albums and currency converters.
>
> Introduction: A widget is an interactive single purpose application
> for displaying and/or updating local data or data on the Web,
> packaged in a way to allow a single download and installation on a
> user's machine or mobile device. A widget may run as a stand alone
> application (meaning it can run outside of a Web browser), or may
> be
> embedded into a Web document. In this document, the runtime
> environment on which a widget is run is referred to as a widget
> user
> agent and a running widget is referred to as an instantiated widget.
> Prior to instantiation, a widget exists as a widget resource. For
> more information about widgets, see the Widget Landscape document.
> ]]
>
> We would appreciate any comments your WG has on this LC document,
> especially those requirements relevant to your WG's domain/scope.
> The
> comment period ends 1 August 2008.
>
> -Regards, Art Barstow
>

Received on Thursday, 26 June 2008 20:58:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:55 GMT