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

Re: [Widgets] Widget Gallery RSS like sharing format

From: Marcos Caceres <marcosc@opera.com>
Date: Wed, 11 Mar 2009 14:34:47 +0100
Message-ID: <b21a10670903110634l47979a6p759cb3a1f7249cb2@mail.gmail.com>
To: SUZANNE Benoit RD-SIRP-ISS <benoit.suzanne@orange-ftgroup.com>
Cc: public-webapps@w3.org
On Wed, Mar 11, 2009 at 2:14 PM, SUZANNE Benoit RD-SIRP-ISS
<benoit.suzanne@orange-ftgroup.com> wrote:
> All,
> Based on our last F2F, we have talked about an RSS like file format that
> would standardise the widget list for various needs. I do not consider the
> following as a formal format proposition but as an input to open the
> discussion as it should probably be written in atom instead of RSS.
>
> So here we go, here is an example of the xml format:
> <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"
>  xmlns:atom="http://www.w3.org/2005/Atom">
>
>  <channel>
>  <title>Djinngo Widget Catalog on vista</title>
>  <atom:link rel="self" href="http://example.com/gallery/"/>
>  <link>http://example.com/gallery/</link>
>  <description><![CDATA[]]></description>
>  <language>en</language>
>
> <item>
>   <id>3_LiveRadio</id>
>   <title><![CDATA[Orange LiveRadio]]></title>
>   <platform>vista</platform>
>  <category>4</category>

What's 4?

>  <version>1.4.0</version>
>  <link>http://example.com/gallery/#widget=3_LiveRadio</link>
>  <guid isPermaLink="true">
>   http://example.com/gallery/#widget=3_LiveRadio</guid>
>  <language>14</language>

What's 14?

>  <description><![CDATA[Orange LiveRadio gadget]]></description>
>  <screenshot>http://example.com/GadgetFactory/widgets/screenshots/liveradio-fr.jpg</screenshot>
>  <author_name><![CDATA[Orange]]></author_name>
>  <pubDate><![CDATA[Fri, 12 Jan 2007 00:00:00 +0100]]></pubDate>
>  <downloads>0</downloads>
>  <download_url>http://download.example.com/Orange-LiveRadio-FR-v2.gadget</download_url>
>  <rating>0.0</rating>
>  </item>
...
>   </channel>
> </rss>
>
>
>
> The idea is to describe the following elements:
> - title: is the widget’s name
> - pubDate: is the date of the publication of the widget
> - guid: defines a unique identifier for the item
> - platform: is the widget’s platform
> - category: is the number corresponding to a category item
> - version: the widget’s version.
> - link: is the link toward the widget page on the Djinngo gallery.
> - language: is the number corresponding to a language, although here we
> should probably use the language format of the P&C spec
> - description: the widget’s description.
> - screenshot: is the direct link to a screenshot of the widget.
> - downloads: the number of downloads for the widget.
> - download_url: is the direct link to download the widget.
> - rating: the rating the widget on the gallery.

Like you suggest, a simple XSLT of the config.xml to ATOM would be the
best option here. However, now we have a real use case for external
package access via a URI scheme:

<screenshot>http://example.com/my.wgy!/screenshot.jpg</screenshot>

Kind regards,
Marcos

-- 
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 11 March 2009 13:35:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:30 GMT