ウィジェット 1.0 要求仕様

W3C草案2009年x月x日

このバージョン

--

最新のバージョン（草案）

http://dev.w3.org/2006/waf/widgets-reqs/

以前のバージョン

--

編者

Marcos Caceres, Opera Software

Mark Priestley, Vodafone

著作権© 2009 W3C^®（マサチューセッツ工科大学、欧州情報科学数学研究コンソーシアム、慶應義塾大学）により、全ての権利が留保される。W3Cの免責、商標、文書利用規定が適用される。

概要

この仕様書では、様々な面で標準化に取り組む必要のあるウィジェット仕様における、要求事項と設計目標について列挙する。ウィジェットとは、ローカルやウェブ上のデータの表示・更新用のインタラクティブな単一用途アプリケーションであり、ユーザの機材あるいはモバイル機器に、単独でダウンロードやインストールできるようにする方法でパッケージされている。ウィジェットの典型的な例としては、時計、CPUゲージ、付箋メモ、バッテリ残量インジケータ、ゲームや、天気予報、ニュースリーダ、電子メールチェッカ、フォトアルバム、通貨変換のようなウェブサービス使用のウィジェットがある。

この文書の位置づけ

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

You can always find the latest Editor's Draft of this document in the W3C's CVS repository; it is updated on a fairly regular basis.

This is the 6 March 2009 Second Last Call Working Draft version of the "Widgets 1.0: Requirements" document. The Last Call period ends on 12 October 2008. This version reflects over two years of gathering and refining requirements for the Widgets 1.0 family of specifications. The requirements were gathered by extensive consultation with W3C members and the public, via the Working Group's mailing lists (WAF archive, WebApps archive). The purpose of this Last Call is to give external interested parties a final opportunity to publicly comment on the list of requirements. The Working Group's goal is to make sure that vendor's requirements for Widgets are complete and have been effectively captured. The Widgets 1.0 family of specifications will set out to address as many requirements as possible (particularly the ones marked with the keywords MUST and SHOULD).

This document is produced by the Web Applications (WebApps) Working Group (WG). This WG is part of the Rich Web Clients Activity and this activity is within the W3C's Interaction Domain. The public is encouraged to send comments to the WebApps Working Group's public mailing list public-webapps@w3.org (archive). See W3C mailing list and archive usage guidelines.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

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), and it is envisioned that the kind of widgets being standardized by this effort will one day be embedded into Web documents. In this document, the runtime environment in which a widget is run is referred to as a widget user agent. Note that running widgets may be the specific purpose of a widget user agent, or it may be a mode of operation of a more generic user agent (e.g. a Web browser). A widget running on a widget user agent is referred to as an instantiated widget. Prior to instantiation, a widget exists as a widget resource. For more information and definitions related to widgets, see the Widget Landscape document.

As argued by the Widget Landscape document, there is currently no formally standardized way to author, package, digitally sign or internationalize a widget resource for distribution and deployment on the Web. In the widget space, although many successful widget user agents are now on the market, widgets built for one widget user agent are generally not able to run on any other widget user agent.

This document lists the design goals and requirements that specifications need to address in order to standardize how widgets are authored/scripted, digitally signed, secured, packaged and deployed in a way that is device independent, follows W3C principles, and is as interoperable as possible with existing market-leading user agents and existing Web browsers.

To be clear, this specification describes the requirements for installable/desktop or mobile widgets (akin to Apple's Dashboard, Opera Widgets, Opera Mobile Widgets. or Yahoo!'s Konfabulator Widgets). This document does not address the requirements of "web widgets", such as iGoogle Gadgets or Windows Live Gadgets, which are being specified by the Open Ajax Alliance's IDE Working Group. Please see the Widget Landscape document for a discussion on the differences between widgets and web widgets.