Re: [widgets] User agent conformance

On Wed, Jun 4, 2008 at 1:38 AM, Fabrice Desré - France Telecom
DR&D/MAPS/AMS <fabrice.desre@orange-ftgroup.com> wrote:
>
>  According to the latest editor's draft (20 may 2008), a conforming widget
> user agent needs to support zip/deflate, png, gif, xml, xmlns and DOM3CORE.
> However, a conforming widget resource can also include other kinds of
> contents (eg. SVG, SMIL, etc.) Thus there is no way in the current draft for
> a user agent to check beforehand if it will actually be able to run the
> widget. A solution could be to add in config.xml the list of additional mime
> types a user agent must process for a given resource :
> <widget xmlns="http://www.w3.org/ns/widgets"
>        id="http://datadriven.com.au/exampleWidget"
>        version="2.0 Beta" height="200" width="200">
>  <name>The example widget!</name>
>  ...
>  <requires mime="image/svg+xml"/>
>  <requires mime="application/smil"/>
> </widget>

As with web documents, I think this is best left to the html
rendering/parsing engine to deal with. In HTML, authors can use
<embed>, <object>, or an <iframe> for those particular MIME types.
With <object>, authors have the potential to provide a fallback.
Authors can also query a widget engine for feature support via
hasFeature(). For example
document.implementation.hasFeature("org.w3c.dom.svg", "1.0"), which
will return either true or false.

So long as a feature is supported, Widget engines that support +xml
can use compound documents directly.

...Just a thought, but another way of doing this might be to allow
have nested <content> elements:

<content type="image/svg+xml" src="svg/clock.svg">
   <content src="html/clock.html"/>
</content>

... maybe something to consider for version 2 of the spec....

>
> Also, in §5.2 [1] it is said that support for text/html is required. Should
> this be added to §3 [2] ?

Done.


-- 
Marcos Caceres
http://datadriven.com.au
http://standardssuck.org

Received on Thursday, 12 June 2008 00:58:15 UTC