Re: CfC to Shelve DAP Permissions API

Sounds like a good plan to me. One question, inline.
—Nick

> On Jun 18, 2015, at 9:33 AM, Frederick Hirsch <w3c@fjhirsch.com> wrote:
> 
> This is a Call for Consensus (CfC) to shelve the original DAP Permissions API, a Working Draft that was published in 2010 [1].
> 
> There is a new FPWD publication of the "Permissions API" [2]  published by the  Web Application Security Working Group [3]  that supersedes the earlier DAP effort.
> 
> To avoid any potential confusion this is a call for consensus to 'shelve' the DAP document.   Concretely this means the following:
> 
> 1. Publish a W3C Note for the DAP 'Permissions API'  with the following changes from the latest WD publication:
> 
> + Note in the Status section "Work on this document has been discontinued and it should not be referenced or used as a basis for implementation."
> 
> + Provide a link to the WebAppSec Permissions API latest published draft in the status section
> 
> + Remove all content apart from the Abstract and Status sections.

Do we typically publish these notes with all the contents removed? It sounds like shelving work and pointing readers to ongoing WebAppSec is certainly appropriate, but I thought we usually included whatever work had been done thus far in a Note when publishing it to close work.

> I have prepared a W3C Note draft (for publication) reflecting these changes: http://dev.w3.org/2009/dap/api-perms/Note.html
> 
> 2. Remove the Permissions API from the DAP Roadmap [4], add to the list of shelved documents (along with link to WebAppSec latest published draft.
> 
> Please respond if you agree (a +1 will suffice) that (a) DAP discontinue work on the Permissions API, and (b) we publish a Note (tentatively on 2 July 2015)  to shelve the draft as noted and (c) we move the Permissions API to the DAP list of shelved documents (noting the WebAppSec link).
> 
> If you have any concerns please respond as well. Silence will be taken as agreement with the CfC.
> 
> Please respond by 25 June (next week).
> 
> Thanks
> 
> regards, Frederick
> 
> Frederick Hirsch
> Chair, W3C Device APIs WG (DAP)
> 
> www.fjhirsch.com
> @fjhirsch
> 
> 
> [1] http://www.w3.org/TR/api-perms/
> 
> [2] http://www.w3.org/TR/permissions/
> 
> [3] http://www.w3.org/2011/webappsec/
> 
> [4] http://www.w3.org/2009/dap/#roadmap