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

RE: [widgets] Making config.xml mandatory

From: David Rogers <david.rogers@omtp.org>
Date: Mon, 9 Mar 2009 13:19:35 -0000
Message-ID: <4C83800CE03F754ABA6BA928A6D94A060195699D@exch-be14.exchange.local>
To: <marcosc@opera.com>, "public-webapps" <public-webapps@w3.org>

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.



-----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

Kind regards,

Marcos Caceres

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

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:14 UTC