http://dev.w3.org/2006/waf/widgets/#the-feature-element

• From: Kai Hendry <hendry@aplix.co.jp>
• Date: Fri, 6 Feb 2009 14:13:46 +0000
• To: public-webapps@w3.org
• Message-ID: <b24851260902060613x302dac1cp37837d551deada45@mail.gmail.com>

Currently a widget developer declaring the dependency on a feature
might simple write:

<feature name="http://bondi.omtp.org/api.geolocation">

Since the required attribute will be unset and as a
http://dev.w3.org/2006/waf/widgets/#boolean-attribute it will default
to false.

So the unwitting developer effectively specified an optional
dependency for his widget, which is not expected default behaviour.


So I would like to propose something syntax like:
<feature name="http://www.w3.org/geo/api/" optional="true" />

In the rare case where the widget developer has accounted for the
possibility the feature might not be available.


And simply specifying <feature name="http://www.w3.org/geo/api/" />
would make that named feature a mandatory requirement for the widget
to function.

If the feature is unavailable, the widget run time should decline to
install the widget.

Received on Friday, 6 February 2009 14:14:32 UTC