- From: David Rogers <david.rogers@omtp.org>
- Date: Mon, 9 Mar 2009 13:19:35 -0000
- To: <marcosc@opera.com>, "public-webapps" <public-webapps@w3.org>
Marcos, As mentioned in the F2F, this is one of the reasons you can see why you need to look at defining content types more closely - you need to decide what a widget 'is' otherwise we're potentially in trouble. I agree with Rainer's point about policy. Thanks, David. -----Original Message----- From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Marcos Caceres Sent: 09 March 2009 12:36 To: public-webapps Subject: [widgets] Making config.xml mandatory Opera would like to make the config file in widgets packages mandatory. Our rationale is that having at least one config.xml file at the root of the widget give a sure way to identify a zip archive as a widget; otherwise arbitrary zip packages with an index.html could be fed to a widget engine and would run with the security privileges of a widget. Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1990 - Release Date: 03/08/09 17:17:00
Received on Monday, 9 March 2009 13:20:20 UTC