W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2008

ISSUE-16: Do widgets need their own URI scheme? [Widgets]

From: Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 26 Jun 2008 08:15:35 +0000 (GMT)
To: public-webapps@w3.org
Message-Id: <20080626081535.9E7C76B62B@tibor.w3.org>

ISSUE-16: Do widgets need their own URI scheme? [Widgets]

http://www.w3.org/2008/webapps/track/issues/

Raised by: Arve Bersvendsen
On product: Widgets

Some considerations here:
1. Widgets, or other locally installed web applications may have multiple instances served from an arbitrary origin: Preinstalled on devices, beamed over bluetooth/IR, installed from a local file system, or over HTTP. Also
2. In general, the resources do need to resolve, as the DOM attributes are resolved, and normalized, so "DSC0201.jpg" - when loaded from the local filesystem - becomes for instance file://localhost/path/to/DSC0201.jpg". The tag: URI scheme specifically says this:

  Unlike most other URIs, tags can only be used as identifiers, and are not
  designed to support resolution.
3. It is desired to shield the widget from the file system of the runtime (e.g. a widget should not be able to discern information about the file system by examining files loaded from within the widget.
4. Widgets should not be able to have unchecked access to resources outside of itself.  Use of the file: scheme makes this (more) difficult.
Received on Thursday, 26 June 2008 08:17:20 GMT

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