ISSUE-24 (api-availability): Should the Widget spec define a mechanism to check for the availability of an API? [Widgets] from Web Application Formats Working Group Issue Tracker on 2008-05-13 (public-appformats@w3.org from May 2008)

From: Web Application Formats Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 13 May 2008 11:29:36 +0000 (GMT)
To: public-appformats@w3.org
Message-Id: <20080513112936.C80DA6B62B@kent.w3.org>

ISSUE-24 (api-availability): Should the Widget spec define a mechanism to check for the availability of an API? [Widgets]

http://www.w3.org/2005/06/tracker/waf/issues/

Raised by: Marcos Caceres
On product: Widgets

This issue was raised during our 6 May 2008 f2f meeting in Dublin. The basic idea is a Widget would have a mechanism to determine if the widget UA supported, for example, some type of Location API. 

See the minutes for the discussion and details:

 http://www.w3.org/2008/05/06-waf-minutes.html#item16

Received on Tuesday, 13 May 2008 11:31:15 UTC