- From: Marcos Caceres <m.caceres@qut.edu.au>
- Date: Mon, 13 Nov 2006 12:43:21 +1000
- To: Ed Voas <voas@yahoo-inc.com>
- CC: public-appformats@w3.org
I'm also with Ed on this one. I think the more generic 'manifest.xml' name makes more sense in this context, as a lot of the actual data in the manifest is not used to directly "configure" the application in any significant way... but then again, it all depends on the definition of "configuration". Marcos Ed Voas wrote: > On Nov 9, 2006, at 9:44 PM, Marcos Caceres wrote: > >> * <application>, or >> >> * <component>, or >> >> * <about>, or >> >> * <manifest>, or >> >> * <metadata>, or >> >> * <configuration> >> > > Hmm. In pondering this I also question the name of the file. Since > this is metadata, I'm thinking it shouldn't even be called config.xml, > but perhaps just manifest.xml. I can see it being used for metadata > and packaging information that user agents can use to pull the Widget > apart and start it up. That said, I am partial to <manifest>. > > -- Ed >
Received on Monday, 13 November 2006 02:43:40 UTC