ISSUE-59: Widgets: do we need to define a mechanism to state that an extension or feature is mandatory?

Widgets: do we need to define a mechanism to state that an extension or feature is mandatory?

State:
CLOSED
Product:
HISTORICAL: Widgets [Bugs and Issues are tracked via Bugzilla https://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG]
Raised by:
Anne van Kesteren
Opened on:
2007-08-08
Description:
Widgets: do we need to define a mechanism to state that an extension or feature is mandatory? Assuming the answer is yes, then how is the set of extensions for features documented (in the manifest file)?
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

Closed during our 27 March 2008 Voice Conference. See the following for details and rationale:

http://www.w3.org/2008/03/27-waf-minutes.html#item03

27 Mar 2008, 12:27:16

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 59.html,v 1.1 2016/01/25 10:26:22 carine Exp $