Hello Benoït,
I like the idea of the role, and it's an elegant way to solve some issues
linked with multiple icons needs (big, small, etc...) So yes, why not define
some standards roles, and if role is not defined, it's a default role which
is taken?
On Tue, Mar 11, 2008 at 11:40 AM, SUZANNE Benoit RD-SIRP-ISS <
benoit.suzanne@orange-ftgroup.com> wrote:
>
> Hi All
> About the icon element, we have not stated what the role should be but I
> can think of the following elements:
>
> >>>>>
> <widget xmlns="http://www.w3.org/ns/widgets"
> id="http://example.org/widget"
> version="2.0 Beta"
> height="200"
> width="200">
> ..../...
> <icon role="small" src="icons/widget-icon.png" />
> <icon role="favicon" src="icons/widget-favicon.png" />
> <icon role="screenshot" src="icons/widget-screenshot.png" />
> .../...
> </widget>
> <<<<<
>
> Best Regards,
> Benoit
>
>
> *Benoit Suzanne
> *Widget Factory Project Manager - Orange Labs - FT/RD/SIRP/SOL/SLAM
> t. +33 (0)145 298 198 - m. +33 (0)680 287 553
> *benoit.suzanne@orange-ftgroup.com
> *
>
>
>
>
--
Thomas Landspurg
CTO
http://www.webwag.com
