W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2015

DAP rechartering

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 18 Jun 2015 16:41:55 +0200
Message-ID: <5582D8B3.4060203@w3.org>
To: W3C Device APIs WG <public-device-apis@w3.org>
Hi all,

As you may know, the charter of our group expires at the end of this 
year; it looks unlikely that all of our ongoing work [1] will be done by 
then.

Assuming we want to finish the said work, we will need to recharter the 
group: given recent evolutions in the charter management practices in 
W3C, I don't expect we could simply extend our charter another time.

Although the end of the year is 6 months away, the rechartering process 
can easily take two months, so it is not too early to think of the 
content of our new charter.

I have thus started a github repository to let us collaborate on an 
updated charter for our group:
   https://github.com/w3c/dap-charter/
   http://w3c.github.io/dap-charter/DeviceAPICharter.html

I started from our existing charter, removed work items that were 
obviously no longer in our target, added details about those we have 
since started working on, and made several additional editorial changes:
   https://github.com/w3c/dap-charter/commits/gh-pages

I have also started filing issues that I feel need to be addressed in 
the new charter:
https://github.com/w3c/dap-charter/issues

The gist of the most substantive of these issues are:
  * With the SysApps Working Group stopping its work, I think it would 
be useful to discuss if any of the work that was assumed to be done in 
SysApps should be reconsidered for DAP, in particular the PIM APIs and 
the messaging API. If not, we should remove them from the list

  * We should also look at other standardization opportunities; for 
instance, new sensor APIs, or maybe standardizing the work done in some 
of the CGs (e.g. Web Bluetooth) [assuming they're interested in such a 
thing]

  * More generally, should we strive for an open-ended charter where 
adding new deliverables that fit the scope of the charter doesn't 
require a rechartering?

Feedback on these issues and on the draft charter overall, here or on 
github would be most welcomed.

Thanks,

Dom

1. http://www.w3.org/2009/dap/#roadmap
Received on Thursday, 18 June 2015 14:43:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:05 UTC