- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Mon, 7 Apr 2008 20:53:10 +1000
- To: "Pollington, David, VF-Group" <david.pollington@vodafone.com>
- Cc: "member-appformats WG" <member-appformats@w3.org>, "WAF WG (public)" <public-appformats@w3.org>
Hi David, > In order to assist Widget discovery, search and cataloguing, perhaps we > should consider adding a Tag element to the Name and Description > elements already specified. Something like: > > The tag Element > > The tag element represents human-readable CSV tags for a widget resource > that can be used, for example, for widget discovery (e.g., search) and > cataloguing. > > Contexts in which this element may be used: > In a widget element. > Content model: > Text. > Occurrences: > Zero, one or more than one (CSV notation) > > I appreciate that such metadata about a Widget could be aggregated on > the hosting server (e.g., when the Widget is uploaded) but embedding the > 'tag' metadata in the Widget itself then also enables viral > distribution. > > If too late in the day for consideration for the 14th April deadline, > then perhaps something we can add in the future. Yeah, I'm reluctant to add new things in at this point. But we should put it for discussion for the F2F in Dublin. FWIW, even if we don't include it, the tag could be part of an extension for the description element: <widgets xmlns="...ns/widgets/" ex:xmlns="foo"> <description>This widget does such and such. Tags: <ex:tag>foo, bar, oof, rab</ex:tag> </description> </widgets> Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au
Received on Monday, 7 April 2008 10:53:45 UTC