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

RE: DAP Roadmap, priorities

From: <Ingmar.Kliche@telekom.de>
Date: Wed, 11 Nov 2009 12:08:37 +0100
Message-ID: <98B37F7D0484184B9DBDCC44B6C8EDA303E245F8@S4DE9JSAAID.ost.t-com.de>
To: <public-device-apis@w3.org>
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.

Thanks
Dzung Tran

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

Hi,

Per my ACTION-60, I have started working on a roadmap for our WG
deliverables at:
http://www.w3.org/2009/dap/#roadmap

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
table.

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.

Dom

1.
http://lists.w3.org/Archives/Public/public-device-apis/2009Sep/att-0050/
Device_APIs_and_Policy_Working_Group_Teleconference_--_16_Sep_2009.htm#i
tem07
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 12:56:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT