W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2022

Re: CFC: Publish Web Share API as a Candidate Recommendation

From: Marcos Caceres <marcosc@apple.com>
Date: Mon, 01 Aug 2022 12:16:28 +1000
To: public-webapps <public-webapps@w3.org>
Message-id: <7868F4BC-D24D-4DD2-9F73-8DD34ECACD4B@apple.com>
Hi All,

The CFC has passed with 11 indications of support. πŸŽ‰

We will now prepared the document for publication and make sure issues we addressed from wide review get appropriately closed [1] (the issues were addressed by the Editors, but the horizontal groups haven’t closed the issues on their side).

If all goes to plan, we should hopefully publish before the TPAC moratorium 🀞.  

Kind regards, 
Marcos 

[1] https://www.w3.org/PM/horizontal/review.html?shortname=web-share

> On 12 Jul 2022, at 3:21 pm, Marcos Caceres <marcosc@apple.com> wrote:
> 
> Dear Working Group Participants, 
> 
> This is a call for consensus (CFC) to publish the "Web Share API" specification as a Candidate Recommendation (CR). The CFC ends at midnight on Friday the 29th of July, 2022. We expect the CR phase to run until after TPAC (~September/October, 2022) to allow implementations to iron out some last remaining interoperability issues. 
> 
> From the abstract: "This specification defines an API for sharing text, links and other content to an arbitrary destination of the user's choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts."
> 
> You can view the latest Working Draft here: https://www.w3.org/TR/web-share/
> 
> The specification has received wide review and is interoperable across all major browser engines and is available on a range of platforms. Further, it has seen significant uptake by web developers and is now a feature of popular websites, such as YouTube.
> 
> However, the specification identifies one feature "at risk":
> 
> β€’ Permissions policy 'self' is at risk (see [at-risk] link below) - due to web compatibility issues.
> 
> Please indicate your support for publishing the specification as a W3C Candidate Recommendation in the Github issue linked below using either the πŸ‘ or πŸ‘Ž (formal objection) reaction buttons of this issue. If you have a formal objection (i.e., you indicate "πŸ‘Ž") to its publication, we kindly ask that you provide a detailed rationale for the objection, either here or in the Github issue below: 
> 
> https://github.com/w3c/web-share/issues/246
> 
> Kind regards,
> Marcos and Leonie (Chairs), and Xiaoqian (Team Contact)
> 
> [at-risk] https://github.com/w3c/web-share/issues/169
Received on Monday, 1 August 2022 02:16:51 UTC

This archive was generated by hypermail 2.4.0 : Monday, 1 August 2022 02:16:53 UTC