Future of Web Crypto API

All,

We closed the Web Cryptography Working Group yesterday.

Thank you to everyone for their efforts.

The Working Group homepage now says:
[[
As of 2017, this Working Group is now closed.

Maintenance for the W3C Recommendation happens under the supervision of 
the Web Security Interest Group.
]]
https://www.w3.org/2012/webcrypto/

Discussion around current and future work for the Web Crypto API should 
be happening on the public-web-security@w3.org mailing list.

Regarding the maintenance of the W3C Recommendation itself, keep the 
following in mind:

1. In-place modification are governed by
[[
The only modifications allowed in place are:

     Fixes to broken markup (e.g., invalid markup)
     Fixed to broken links (i.e., URIs)
     Fixes to broken style sheets
     Some visible status updates, such as indicating newer versions
     An individual's name upon request to a W3C Ombudsperson
]]
https://www.w3.org/2003/01/republishing/

2. Republication of a new Recommendation with *only* editorial changes 
is governed by (starting March 1st, 2017):

[[
Editorial changes to a Recommendation require no technical review of the 
proposed changes. A Working Group, provided there are no votes against 
the resolution to publish may request publication of a Recommendation or 
W3C may publish a Recommendation to make this class of change without 
passing through earlier maturity levels.
]]
https://www.w3.org/2017/Process-20170301/#revised-rec

Since the Working Group is closed, the request for republication would 
have to go to W3C (more that in later communications).

3. Republication of a new Recommendation with substantive changes is 
governed by (no change since W3C Process 2015):
[[
To make corrections to a Recommendation that produce substantive changes 
but do not add new features, or where there were votes against 
publishing the corrections directly as a Recommendation, a Working Group 
may request publication of a Candidate Recommendation, without passing 
through earlier maturity levels.
]]
https://www.w3.org/2017/Process-20170301/#revised-rec

In other words, this is not a current possibility for the Web 
Cryptography API since the Working Group is closed.

4. Publication of a new Recommendation with new features is governed by 
(no change since W3C Process 2015):
[[
For changes which introduces a new feature or features, W3C must follow 
the full process of advancing a technical report to Recommendation 
beginning with a new First Public Working Draft.
]]
https://www.w3.org/2017/Process-20170301/#revised-rec

Philippe

Received on Wednesday, 8 February 2017 15:49:51 UTC