W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [widgets] <option>s on <feature>s

From: Arve Bersvendsen <arveb@opera.com>
Date: Wed, 18 Mar 2009 16:37:46 +0100
To: "Robin Berjon" <robin@berjon.com>, "Marcos Caceres" <marcosc@opera.com>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <op.uqzu07ncbyn2jm@galactica>
On Wed, 18 Mar 2009 16:19:34 +0100, Robin Berjon <robin@berjon.com> wrote:

> On Mar 18, 2009, at 15:38 , Marcos Caceres wrote:
>> It might be good to add an <option>s element on the <feature> element  
>> to allow options to be set for features using name-value pairs. For  
>> example:
>>
>> <feature name="http://clothing.com/api">
>> 	<option name="fancy" value="pants"/>
>> 	<option name="color" value="green"/>
>> </feature>
>
> Do you have some examples that involve things that aren't pants?

Does this suffice? 

<feature name="url_describing_filesystem_api">
  <option name="music" value="read" />
  <option name="video" value="read write" />
</feature>

The intent would be to allow a widget UA to allow native UI for selecting this, not dependent on for instance browseForDirectory().

-- 
Arve Bersvendsen

Developer, Opera Software ASA, http://www.opera.com/
Received on Wednesday, 18 March 2009 15:38:29 GMT

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