ISSUE-18: Need to define a mechanism to check for the availability of an API
api-availability
Need to define a mechanism to check for the availability of an API
- State:
- CLOSED
- Product:
- HISTORICAL: Widgets [Bugs and Issues are tracked via Bugzilla https://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG]
- Raised by:
- Marcos Caceres
- Opened on:
- 2008-06-26
- Description:
- This issue was first raised 13 May 2008 by Marcos 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 - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-18 (api-availability): Need to efine a mechanism to check for the availability of an API [Widgets] (from art.barstow@nokia.com on 2008-08-30)
- Re: ISSUE-18 (api-availability): Need to efine a mechanism to check for the availability of an API [Widgets] (from art.barstow@nokia.com on 2008-06-26)
- ISSUE-18 (api-availability): Need to efine a mechanism to check for the availability of an API [Widgets] (from sysbot+tracker@w3.org on 2008-06-26)
Related notes:
This issue has been closed, based on the WG's agreement on August 28. Please see the following for details:
http://www.w3.org/2008/08/28-wam-minutes.html#item02
-Regards, Art Barstow
This issue has been closed, based on the WG's agreement on August 28. Please see the following for details:
http://www.w3.org/2008/08/28-wam-minutes.html#item02
-Regards, Art Barstow
Display change log