W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

[widgets] Feature Access Declarations requirement

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Wed, 8 Oct 2008 15:15:02 +0100
Message-ID: <b21a10670810080715p6572fb66xdd0c8d837f03aa1b@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>

Hi,
To more clearly reflect the current addition of the <feature> element,
I have drafted the following requirement for the Widgets Requirement
document.

R21. Feature Access Declarations
A conforming specification MUST specify or recommend a means to allow
authors to declare that an instantiated widget will require access to
device specific standardized features or proprietary features (e.g. a
proprietary API to access the camera on a device). A conforming
specification MUST be specified in such a way that fallback
relationships can be declared so that if one feature is unavailable,
another can be declared as a possible substitute. In addition, A
conforming specification MUST provide authors with a means of stating
which features are optional and which features are mandatory for a
widget to run.

Motivation:
Device independence, ease of use, security, and interoperability.

Rationale:
To allow authors to securely request access to device specific
services and features, and to allow widgets to use proprietary
features but with a degree of graceful degradation if a feature is
unavailable to a particular widget user agent.


Comments?

I've also moved the "Security Declarations" requirement to the
Security section (it's now R50).

Kind regards,
Marcos
-- 
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 8 October 2008 14:15:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:28 GMT