Another abandoned server code base... this is kind of an ancestor of taskrambler.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

357 lines
20 KiB

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><!-- Generated from data/head.php, ../../smarty/{head.tpl} --><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>Widgets Current Status - W3C</title><link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="handheld, all" /><style type="text/css" media="print, screen and (min-width: 481px)" xml:space="preserve">
@import url("/2008/site/css/advanced");
</style><link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="handheld, only screen and (max-device-width: 480px)" /><meta name="viewport" content="width=device-width" /><link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" /><link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon" /></head><body id="www-w3-org" class="w3c_public"><div id="w3c_container">
<!-- Generated from data/mast.php, ../../smarty/{mast.tpl} -->
<div id="w3c_mast">
<!-- #w3c_mast / Page top header -->
<h1 class="logo">
<a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C" /></a>
<span class="alt-logo">W3C</span>
</h1>
<div id="w3c_nav">
<!-- Search form and media selection -->
<form action="/Help/search" method="get" enctype="application/x-www-form-urlencoded"><div class="w3c_sec_nav"><!-- --></div><ul class="main_nav"><li class="first-item">
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li><li class="search-item">
<div id="search-form">
<input tabindex="3" class="text" name="q" value="" title="Search" type="text" />
<button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17" /></button>
</div>
</li></ul></form>
</div>
<!-- /end #w3c_nav -->
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<div id="w3c_logo_shadow" class="w3c_leftCol">
<img height="32" alt="" src="/2008/site/images/logo-shadow" />
</div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
<br /></div>
<div class="w3c_mainCol">
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<ul class="bct"> <!-- .bct / Breadcrumbs -->
<li class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_content_body">Skip</a></li>
<li><a href="/">W3C</a>&#xA0;<span class="cr">&#xBB;</span>&#xA0;</li>
<li><a href="/standards/">Standards</a>&#xA0;<span class="cr">&#xBB;</span>&#xA0;</li>
<li><a href="/TR/">All&#xA0;Standards&#xA0;and&#xA0;Drafts</a>&#xA0;<span class="cr">&#xBB;</span>&#xA0;</li>
<li class="current">Widgets Current Status</li>
</ul>
</div>
</div>
<h1 class="title">Widgets Current Status</h1>
<ul class="w3c_toc">
<li>
<a href="#completed">completed&#xA0;work</a>
&#x2014;&#xA0;including&#xA0;<a href="#stds">standards</a>
<span class="bullet">&#x2022; </span>
</li>
<li>
<a href="#drafts">drafts</a>
</li>
</ul>
<div id="w3c_content_body">
<div id="w3c_generated_status">
<p id="w3c_toggle_include" class="default_open intro tPadding">This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: <a href="http://www.w3.org/standards/webdesign/script">Scripting and Ajax</a>.</p>
<h2 id="completed">Completed Work</h2>
<p>
<a href="/TR/tr-technology-stds">W3C Recommendations</a> have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation
Track</a>.</p>
<p>
<a href="/2005/10/Process-20051014/tr.html#q75">Group Notes</a> are <em>not</em> standards and do not
have the same level of W3C endorsement.</p>
<h3 id="stds">Standards</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/widgets" title="Widget Packaging and XML Configuration publication history">2011-09-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2011/REC-widgets-20110927/">Widget Packaging and XML Configuration</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=widgets">translations</a>
&#xB7;
<a href="http://dev.w3.org/2006/waf/widgets/errata.html">errata</a>
</p>
<div class="expand_description">
<p>This specification standardizes a general purpose packaging format for installable client-side Web applications (widgets). Widgets can be authored with Web standards, such as HTML, CSS, and JavaScript, and have many use cases: this format has been successfully used as the container format for web browser extensions, as standalone applications on devices, and even as server-side applications that get embedded into Web pages.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="notes">Group Notes</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/widgets-reqs" title="Requirement For Standardizing Widgets publication history">2011-09-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2011/NOTE-widgets-reqs-20110927/">Requirement For Standardizing Widgets</a>
</h4>
<div class="expand_description">
<p>This document lists the design goals and requirements that were used by the Web Applications Working Group to standardize installable client-side Web applications (widgets).</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/dap-policy-reqs" title="Device API Access Control Use Cases and Requirements publication history">2011-03-17</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2011/NOTE-dap-policy-reqs-20110317/">Device API Access Control Use Cases and Requirements</a>
</h4>
<div class="expand_description">
<p>This document defines requirements for controlling access to device APIs, illustrated by corresponding use cases.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/dap-privacy-reqs" title="Device API Privacy Requirements publication history">2010-06-29</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/">Device API Privacy Requirements</a>
</h4>
<div class="expand_description">
<p>This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/dap-api-reqs" title="Device APIs Requirements publication history">2009-10-15</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/">Device APIs Requirements</a>
</h4>
<div class="expand_description">
<p>These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="drafts">Drafts</h2>
<p>Below are draft documents:
<a href="/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendations</a>, <a href="/2005/10/Process-20051014/tr.html#RecsCR">Candidate Recommendations</a>, <a href="/2005/10/Process-20051014/tr.html#RecsWD">other Working Drafts</a>.
Some of these may become Web Standards through the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation Track
process</a>. Others may be published as Group Notes or
become obsolete specifications.</p>
<h3 id="pr">Proposed Recommendations</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/widgets-access" title="Widget Access Request Policy publication history">2011-12-13</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is PR" href="http://www.w3.org/TR/2011/PR-widgets-access-20111213/">Widget Access Request Policy</a>
</h4>
<div class="expand_description">
<p>This specification defines the security model controlling network access from within a widget, as well as a method for widget authors to request that the user agent grant access to certain network resources or sets thereof.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/widgets-digsig" title="XML Digital Signatures for Widgets publication history">2011-08-11</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is PR" href="http://www.w3.org/TR/2011/PR-widgets-digsig-20110811/">XML Digital Signatures for Widgets</a>
</h4>
<div class="expand_description">
<p>This document defines a profile of the <cite>XML-Signature Syntax and
Processing</cite> specification to allow a widget resource to be
digitally signed.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/view-mode" title="The 'view-mode' Media Feature publication history">2011-08-11</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is PR" href="http://www.w3.org/TR/2011/PR-view-mode-20110811/">The 'view-mode' Media Feature</a>
</h4>
<div class="expand_description">
<p>
This specification defines a media feature to match the different visual presentation modes that can be applied to web applications and thereby apply different styling based on these different modes using CSS Media Queries.
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="cr">Candidate Recommendations</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/widgets-apis" title="Widget Interface publication history">2011-12-13</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is CR" href="http://www.w3.org/TR/2011/CR-widgets-apis-20111213/">Widget Interface</a>
</h4>
<div class="expand_description">
<p>This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget&#x2019;s metadata and persistently storing data.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="wd">Other Working Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/widgets-uri" title="Widget URI scheme publication history">2011-09-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-widgets-uri-20110927/">Widget URI scheme</a>
</h4>
<div class="expand_description">
<p>This specification defines the widget URI scheme that is used to address resources inside a widget package.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/widgets-updates" title="Widget Updates publication history">2010-09-28</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2010/WD-widgets-updates-20100928/">Widget Updates</a>
</h4>
<div class="expand_description">
<p>This specification defines a process and a document format to allow a user agent to update an installed widget package with different version of a widget package.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/widgets-land" title="Widgets 1.0: The Widget Landscape (Q1 2008) publication history">2008-04-14</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2008/WD-widgets-land-20080414/">Widgets 1.0: The Widget Landscape (Q1 2008)</a>
</h4>
<div class="expand_description">
<p>This document surveys a group of market-leading widget user agents with the aim to
inform the requirements of the <cite>Widgets 1.0: Requirements</cite> document. The
survey exposes commonalities and fragmentation across widget user agents, and discusses
how fragmentation currently affects, amongst other things, authoring, security,
distribution and deployment, internationalisation and the device-independence of widgets.
The document concludes by making a set of recommendations on what aspects of widgets
require standardization to reduce fragmentation to ultimately standardize a
cross-platform widget solution.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div><!-- Generated from data/footer.php, ../../smarty/{footer-block.tpl} --><div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav"><li>
<a href="/">Home</a>
</li><li>
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav"><li>
<a href="/Consortium/contact">Contact</a>
</li><li>
<a accesskey="0" href="/Help/">Help and FAQ</a>
</li><li>
<a href="/Consortium/sponsor/">Sponsor / Donate</a>
</li><li>
<a href="/Consortium/siteindex">Site Map</a>
</li><li>
<address id="w3c_signature">
<a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)</address>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav"><li>
<a href="http://twitter.com/W3C" title="Follow W3C on Twitter">
<img src="/2008/site/images/twitter-bird" alt="Twitter" width="78" height="83" class="social-icon" />
</a>
<a href="http://identi.ca/w3c" title="See W3C on Identica">
<img src="/2008/site/images/identica-logo" alt="Identica" width="91" height="83" class="social-icon" />
</a>
</li></ul>
</div>
<p class="copyright">Copyright &#xA9; 2012 W3C <sup>&#xAE;</sup> (<a href="http://www.csail.mit.edu/">
<acronym title="Massachusetts Institute of Technology">MIT</acronym>
</a>, <a href="http://www.ercim.eu/">
<acronym title="European Research Consortium for Informatics and Mathematics"> ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div><!-- /end #footer --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><div id="w3c_scripts">
<script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><!-- --></script>
</div></body></html>