Plan to progress "wake lock"/"standby API"

The “Call for potential DAP charter additions” completed with general agreement on interest in one item, the “wake lock”/“standby API”.

I propose that we can begin work on this item under the existing charter[1], as it can be considered part of the existing deliverable  

"An API to react to a device power status.”

The reason is that the purpose of the wake lock API is to  “prevent a device from entering a power-saving state”, clearly related to reacting to device power status.

The alternative would be a more lengthy re-chartering, which I do not believe is necessary in this case.

This approach means that the WG would work on an editors draft, then agree to a FPWD transition. 

Please indicate any support or concern with this approach to go forward.


regards, Frederick

Frederick Hirsch, Nokia
Chair DAP


On Jun 23, 2014, at 12:00 PM, Frederick Hirsch <> wrote:

> All:
> We have previously discussed the possibility of adding a "Standby API” deliverable to the DAP charter [1].  We are asking if there are any other potential DAP work items to add to the charter, as this might affect how we approach updating the charter.
> I asked in the message sent 28 May, but have not received any suggested items.
> This is a request to share any potential charter additions for consideration. Please respond by 7 July 2014 (2 weeks) either on the public list (preferred) or privately to myself and Dom.
> Thanks
> regards, Frederick
> Frederick Hirsch, Nokia
> Chair DAP
> @fjhirsch
> [1]

Received on Monday, 11 August 2014 19:20:26 UTC