W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

RE: DAP Roadmap, priorities

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Wed, 11 Nov 2009 09:50:58 -0800
To: "Ingmar.Kliche@telekom.de" <Ingmar.Kliche@telekom.de>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312C81D2B6C@orsmsx501.amr.corp.intel.com>
We should take a look at Gears Camera API:


I also have extensive experience with camera system level libraries on Linux with LibV4L(x) which should give some insights into requirements and API.

Dzung Tran

-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Ingmar.Kliche@telekom.de
Sent: Wednesday, November 11, 2009 03:09 AM
To: public-device-apis@w3.org
Subject: RE: DAP Roadmap, priorities

I would like to support the effort around photo/audio/video capture and
help editing this spec in particular. I could also come up with a
strawman proposal.

In this context we should also look at the latest camera API proposed
for BONDI 1.1: http://bondi.omtp.org/1.1/CR/apis/camera.html

It seems worth to mention that the getSupportedFeatures()/setFeature()
pair of functions tries to solve the problem of arbitrary
capability/feature/format variants of cameras.  
- Ingmar.

-----Original Message-----
From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of Tran, Dzung D
Sent: Tuesday, November 10, 2009 3:48 PM
To: Dominique Hazael-Massieux; public-device-apis
Subject: RE: DAP Roadmap, priorities

I would second the important of having photo/audio/video capture API. I
could volunteer to take a stab at this API if there is no other interest
in doing it.

Dzung Tran

-----Original Message-----
From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of Dominique
Sent: Tuesday, November 10, 2009 02:29 AM
To: public-device-apis
Subject: DAP Roadmap, priorities


Per my ACTION-60, I have started working on a roadmap for our WG
deliverables at:

I have listed at the top the APIs that were identified as our priorities
in one of our early teleconfs [1], although we didn't make it a formal
resolution as far as I can tell. The APIs we agree to work on in
priority [2] are:
* Contacts
* Calendar
* Filesystems
* Messaging

Note that at this time, we only have active work on the Contacts API in
that list, and some discussions around Filesystems - the lack of work on
the two others is somewhat worrying. I think it would be useful to get
people volunteering to come up with Editors drafts for Calendar and
Messaging at the very least.

I have heard several people thinking that the photo/audio/video capture
API should also be a priority (myself included, actually), so maybe this
is something we should reconsider.

I would be also useful if the WG could approve the rough schedule
(ideally after having agreed on more specifics for the priority APIs).

I haven't put any policy-related spec in the table, since I don't think
we have a very clear idea on how they are going to be articulated at
this point; but when/if we do, we should definitely add them to the

Ideally, we should discuss that roadmap each time we fall behind
schedule on any of the priority items and update it after that
discussion. I hope the Chairs can take responsibility for this, but I'll
try to watch this as well.

I have also started listing API that we will not work on (per previous
discussions), as well as APIs that have been suggested for future work
(which matches Robin's ACTION-56), although that latter list might be
usefully moved to a wiki page as suggesting in the said action item.


2. this also takes of Robin's ACTION-55; this might also take care of
Frederick's ACTION-57, although this is not in the wiki
Received on Wednesday, 11 November 2009 17:51:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:45:56 UTC