- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Mon, 4 Jun 2007 10:15:59 -0400
- To: Marcos Caceres <m.caceres@qut.edu.au>, public-appformats@w3.org
Marcos, All - regarding R#27 of the 30 May (v1.34) Editor's Draft of
the Widgets Requirements doc:
<http://dev.w3.org/cvsweb/2006/waf/widgets-reqs/Overview.html>
It currently has two Issues:
[[
ISSUE: Most widget engines provide api to access system services,
however this requirement is beyond the scope of the Widget
Specification. However, there are other working groups working on
this issue such as Ubuquitious Web Applications Working Group, and
the Open Mobile Alliance (OMA).
ISSUE: This requirement needs to address how services, like the
camera, SMS, and device specific services are made available to
scripts. There are a number of options here: either we either start
defining a core set of APIs for things like the camera (eg.
Camera.takePicture(), Camera.activate(), Camera.startRecording(),
etc.), or we have some sort of generic mechanism for getting at
services (eg. getServiceProvider('Camera'); ) Please send us your
feedback.
]]
I think the requirement needs to be relaxed here to accommodate user
agents that do not provide any APIs to device/platform services.
Thus, I would re-word the above to something like:
[[
Widget engines may provide APIs to access system services.
The specification of APIs for systems services is beyond the scope of
the WAF WG's Widget Specification. However, there are other open
standards organizations working on such APIs i.e. the W3C's
Ubuquitious Web Applications Working Group [UWA] and the Open Mobile
Alliance (OMA) [OMA].
One example of a system service is a device's camera with APIs such
as Camera.takePicture(), Camera.activate(), Camera.startRecording(),
etc.
]]
Regards,
Art Barstow
---
Received on Monday, 4 June 2007 14:16:48 UTC