- From: Marcos Caceres <m.caceres@qut.edu.au>
- Date: Tue, 5 Jun 2007 13:39:39 +1000
- To: "Arthur Barstow" <art.barstow@nokia.com>
- Cc: public-appformats@w3.org
- Message-ID: <b21a10670706042039g4c15cc81qcbafacacd1492f82@mail.gmail.com>
Hi Art, On 6/5/07, Arthur Barstow <art.barstow@nokia.com> wrote: > > 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> > > [[ > 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. > ]] Ok, I've rewritten it to read: [[ A widget engine may provide APIs to access system resources and services. Examples of device-specific services and resources that could be made available through script include cameras, SMS, and the address book. However, this requirement is beyond the scope of the Web Application Format [Working Group Charter]. There are other working groups working on this requirements such as Ubiquitous Web Applications Working Group [UWAWG], and the Open Mobile Alliance [OMA]. ]] Does anyone know exactly which OMA working group is working on this requirement? Kind regards, -- Marcos Caceres http://datadriven.com.au
Received on Tuesday, 5 June 2007 03:39:43 UTC