- From: Marcos Caceres <marcosc@opera.com>
- Date: Wed, 18 Mar 2009 15:45:12 +0100
- To: public-webapps <public-webapps@w3.org>
On Wed, Mar 18, 2009 at 3:38 PM, Marcos Caceres <marcosc@opera.com> 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> > > Thoughts? comments? (displaying multiple personalities here...) The above could also be achieved by using query strings <feature name="http://clothing.com/api?pants=fancy&color=green"/> Or another way: <feature name="http://clothing.com/api/pants/facy/green"/> But I think using an <option> element is easier to work with... -- Marcos Caceres http://datadriven.com.au
Received on Wednesday, 18 March 2009 14:45:55 UTC