Update migrated WICG specs, CORS and Notifications (#469)

This update updates the URL of WICG specs that have recently migrated to a
Working Group or whose repo name has changed:

- Migrations to the Web Applications Working Group: Badging API and Web Share
Target API
- Repo name changes: Web Background Synchronization and Input Device
Capabilities

Relevant text moved to "in progress" sections for migrations.

This update also makes CORS a feature of the Fetch spec and switches the
Notifications API to the WHATWG version (see #467)

A few new implementation statuses seem to be reported by the Edge status
platform, this update also takes these new statuses into account.

data/background-sync.json

@@ -1,6 +1,5 @@
 {
-  "url": "https://wicg.github.io/BackgroundSync/spec/",
-  "title": "Web Background Synchronization",
+  "url": "https://wicg.github.io/background-sync/spec/",
   "impl": {
     "caniuse": "background-sync",
     "chromestatus": 6170807885627392,

data/badging.json

@@ -1,6 +1,12 @@
 {
-  "url": "https://wicg.github.io/badging/",
+  "url": "https://w3c.github.io/badging/",
   "title": "Badging API",
+  "wgs": [
+    {
+      "label": "Web Applications Working Group",
+      "url": "https://www.w3.org/2019/webapps/"
+    }
+  ],
   "impl": {
     "chromestatus": 6068482055602176
   }

data/fetch.json

@@ -6,5 +6,11 @@
     "chromestatus": 6730533392351232,
     "edgestatus": "Fetch API",
     "webkitstatus": "specification-fetch"
+  },
+  "features": {
+    "cors": {
+      "title": "CORS protocol",
+      "url": "#http-cors-protocol"
+    }
   }
 }

data/inputdevice.json

@@ -1,5 +1,5 @@
 {
-  "url": "https://wicg.github.io/InputDeviceCapabilities/",
+  "url": "https://wicg.github.io/input-device-capabilities/",
   "impl": {
     "chromestatus": 5681847971348480
   }

data/notifications.json

@@ -1,5 +1,6 @@
 {
-  "url": "https://www.w3.org/TR/notifications/",
+  "url": "https://notifications.spec.whatwg.org/",
+  "title": "Notifications API",
   "impl": {
     "caniuse": "notifications",
     "chromestatus": 5064350557536256,

data/web-share-target.json

@@ -1,5 +1,12 @@
 {
-  "url": "https://wicg.github.io/web-share-target/",
+  "url": "https://w3c.github.io/web-share-target/",
+  "title": "Web Share Target API",
+  "wgs": [
+    {
+      "label": "Web Applications Working Group",
+      "url": "https://www.w3.org/2019/webapps/"
+    }
+  ],
   "impl": {
     "chromestatus": 5662315307335680
   }

games/network.html

@@ -18,7 +18,7 @@ <h2>Well-deployed technologies</h2>
         </div>
 
         <div data-feature="Cross-domain requests">
-          <p>By default, browsers do not allow to make request across different domains (or more specifically, across different origins, a combination of the protocol, domain and port) from a single Web page; this rule protects users from having a Web site abusing their credentials and stealing their data on another Web site. Sites can opt-out of that rule by making use of the <a data-featureid="cors">Cross-Origin Resource Sharing</a> (CORS) mechanism, opening up much wider cooperation across Web applications and services. Note the W3C version of the CORS specification does not reflect current implementations and will be obsoleted. The CORS mechanism is now a core part of the on-going <a href="https://fetch.spec.whatwg.org/">Fetch specification</a> in the WHATWG.</p>
+          <p>By default, browsers do not allow to make request across different domains (or more specifically, across different origins, a combination of the protocol, domain and port) from a single Web page; this rule protects users from having a Web site abusing their credentials and stealing their data on another Web site. Sites can opt-out of that rule by making use of the <a data-featureid="fetch/cors">Cross-Origin Resource Sharing</a> (CORS) mechanism, opening up much wider cooperation across Web applications and services.</p>
         </div>
 
         <div data-feature="Server-pushed requests">

games/network.ja.html

@@ -18,7 +18,7 @@ <h2>実装されている仕様</h2>
         </div>
 
         <div data-feature="Cross-domain requests">
-          <p>既定では、ブラウザはドメイン間 (正確にはオリジン、プロトコル・ドメイン・ポートの異なる組み合わせです) にわたるリクエストを一つのウェブページから行うことはできず、この規則によりユーザはあるウェブサイトから他のサイトの認証情報を悪用したりデータを盗んだりという危険から保護されます。サイトは <a data-featureid="cors">Cross-Origin Resource Sharing</a> (CORS) の機構を利用してこの規則の除外規定を行うことができ、より広い範囲のウェブアプリケーションやサービスに開放することができます。注: W3C 版の CORS 仕様は現在の実装を反映しておらず廃止予定です。CORS 仕様は、WHATWG の <a href="https://fetch.spec.whatwg.org/">Fetch 仕様</a> のコアに入りました。</p>
+          <p>既定では、ブラウザはドメイン間 (正確にはオリジン、プロトコル・ドメイン・ポートの異なる組み合わせです) にわたるリクエストを一つのウェブページから行うことはできず、この規則によりユーザはあるウェブサイトから他のサイトの認証情報を悪用したりデータを盗んだりという危険から保護されます。サイトは <a data-featureid="fetch/cors">Cross-Origin Resource Sharing</a> (CORS) の機構を利用してこの規則の除外規定を行うことができ、より広い範囲のウェブアプリケーションやサービスに開放することができます。</p>
         </div>
 
         <div data-feature="Server-pushed requests">

mobile/lifecycle.html

@@ -25,6 +25,7 @@ <h2>Well-deployed technologies</h2>
         <h2>Technologies in progress</h2>
         <div data-feature="Packing">
           <p>Whether packaged or not, users rely on a variety of metadata (name, icons) to identify the apps they want to use among their list of regularly used applications. The <a data-featureid="appmanifest">Web App Manifest</a> specification lets developers group all these metadata into a single JSON file.</p>
+          <p>The <a data-featureid="badging">Badging API</a> defines a more subtle notification mechanism than <a href="https://www.w3.org/TR/notifications/">Web Notifications</a>, allowing Web applications that have been installed on the device (e.g. through a manifest file) to set an application-wide badge, typically shown next to the application's icon on the home screen, to notify the user when the state of the application has changed and might require their attention (e.g. a new message has arrived).</p>
         </div>
 
         <div data-feature="Offline Web Apps">
@@ -38,6 +39,7 @@ <h2>Technologies in progress</h2>
 
         <div data-feature="Sharing content">
           <p>The <em>share action</em> is a common paradigm on mobile devices to pass content across application boundaries, for instance to post a URL or an image to one's favorite social network application. The <a data-featureid="web-share">Web Share API</a> specification allows a Web application to share text, links and other content to an arbitrary destination of the user's choice. The API is a more focused version of the <a href="https://plus.google.com/116171619992010691739">Web Intents</a> proposal, which was abandoned end of 2012, in part because its genericity triggered user experience issues.</p>
+          <p>The <a data-featureid="web-share-target">Web Share Target API</a> proposal allows web applications to declare, in their application manifest, that they can receive content shared from other applications. This allows Web applications, that the user chose to install, to be listed among other native applications in share menus.</p>
         </div>
 
         <div data-feature="Geofencing">
@@ -50,17 +52,12 @@ <h2>Exploratory work</h2>
 
         <div data-feature="Packing">
           <p>The <a data-featureid="packaging">Web Packaging</a> document describes use cases for a new package format for web sites and applications and outlines such a format.</p>
-          <p>The <a data-featureid="badging">Badging API</a> defines a more subtle notification mechanism than <a href="https://www.w3.org/TR/notifications/">Web Notifications</a>, allowing Web applications that have been installed on the device (e.g. through a manifest file) to set an application-wide badge, typically shown next to the application's icon on the home screen, to notify the user when the state of the application has changed and might require their attention (e.g. a new message has arrived).</p>
         </div>
 
         <div data-feature="State transition">
           <p>Applications running on mobile devices can go through different application states, from running to being idle, paused, stopped, discarded, or terminated. Transitions between these states are triggered by the underlying operating system, and hidden from web applications. The <a data-featureid="page-lifecycle">Page Lifecycle</a> proposal seeks to expose application state transitions to applications so that these applications can persist/restore state, enable/disable use of network, etc.</p>
         </div>
 
-        <div data-feature="Sharing content">
-          <p>The <a data-featureid="web-share-target">Web Share Target API</a> proposal allows web applications to declare, in their application manifest, that they can receive content shared from other applications. This allows Web applications, that the user chose to install, to be listed among other native applications in share menus.</p>
-        </div>
-
         <div data-feature="Seamless navigation">
           <p>Various sites embed content from a third party origin (e.g. news content) within their own user interface, or load third party content into an iframe to provide a faster, reliable loading experience, which is particularly crucial on mobile devices. One main drawback of this approach is that the third party's origin is not preserved: only the first party's origin appears in the address bar, which makes it difficult for users to identify the provenance and trustworthiness of the content they are browsing. Another drawback is that the third party page cannot leverage client-side resources and permissions that are attached to their origin. <a data-featureid="portals">Portals</a> is a proposal for enabling seamless navigations between sites or pages. In particular, it enables a page to show another page as an inset and perform a seamless transition between an inset state and a navigated state, thus solving the origin issues mentioned above.</p>
         </div>

mobile/lifecycle.zh.html

@@ -25,6 +25,7 @@ <h2>广泛部署的技术</h2>
         <h2>开发中的技术</h2>
         <div data-feature="打包">
           <p>无论是否打包，用户都依靠各种元数据（名称、图标）在常用应用列表中来识别他们想要使用的应用。<a data-featureid="appmanifest">Web应用清单</a>规范允许开发人员将所有这些元数据放在一个 JSON 文件中。</p>
+          <p>除了<a href="https://www.w3.org/TR/notifications/">Web通知</a>以外，<a data-featureid="badging">标记 API</a>定义了另一种通知机制，允许已经安装在设备上的 Web 应用（例如通过清单文件）设置一个标记，通常显示在主屏幕上应用程序的图标旁边，在应用程序的状态发生变化时通知用户可能需要注意的信息（如新消息）。</p>
         </div>
 
         <div data-feature="离线 Web 应用">
@@ -38,6 +39,7 @@ <h2>开发中的技术</h2>
 
         <div data-feature="内容分享">
           <p><em>分享操作</em>是移动设备上通过跨应用边界传递内容的常见范例，例如将 URL 或图像发布到自己最喜欢的社交网络应用中。<a data-featureid="web-share">Web分享API</a>规范允许 Web 应用将文本、链接和其他内容分享到用户选择的任意目的地。该 API 是<a href="https://plus.google.com/116171619992010691739">Web Intents</a>提案的一个更有针对性的版本，Web Intents在2012年停止开发，部分原因是它的一般性引发了用户体验问题。</p>
+          <p><a data-featureid="web-share-target">Web分享目标API</a>建议允许Web应用在其应用清单中声明其可接收来自其他应用的内容。这允许用户选择安装的Web应用在分享菜单中被其他本地应用列出。</p>
         </div>
 
         <div data-feature="地理围栏">
@@ -50,17 +52,12 @@ <h2>探索性工作</h2>
 
         <div data-feature="打包">
           <p><a data-featureid="packaging">Web 打包</a>文档描述了用于网站和应用的新包格式的用例，并概述了这种格式。</p>
-          <p>除了<a href="https://www.w3.org/TR/notifications/">Web通知</a>以外，<a data-featureid="badging">标记 API</a>定义了另一种通知机制，允许已经安装在设备上的 Web 应用（例如通过清单文件）设置一个标记，通常显示在主屏幕上应用程序的图标旁边，在应用程序的状态发生变化时通知用户可能需要注意的信息（如新消息）。</p>
         </div>
 
         <div data-feature="状态转换">
           <p>在移动设备上运行的应用可以通过不同的状态，从运行到空闲、暂停、停止、丢弃或终止。这些状态之间的转换由底层操作系统触发，并从 Web 应用中隐藏。<a data-featureid="page-lifecycle">页面生命周期</a>方案旨在向应用公开状态转换，以便这些应用能够保持/恢复状态、启用/禁用网络等。</p>
         </div>
 
-        <div data-feature="内容分享">
-            <p><a data-featureid="web-share-target">Web分享目标API</a>建议允许Web应用在其应用清单中声明其可接收来自其他应用的内容。这允许用户选择安装的Web应用在分享菜单中被其他本地应用列出。</p>
-        </div>
-
         <div data-feature="无缝切换">
           <p>很多网站会在其自己的用户界面内嵌入来自第三方来源的内容（例如新闻内容），或者将第三方内容加载到 iframe 中以提供更快、可靠的加载体验，这对于移动设备尤其重要。这种方法的一个主要缺点是不保留第三方的来源：只有第一方的来源出现在地址栏中，这使得用户难以识别他们正在浏览的内容的出处和可信度。另一个缺点是第三方页面无法利用附加到其源的客户端资源和权限。<a data-featureid="portals">Portals</a>是一个在网站或网页之间实现无缝切换的提案，它使一个页面能够嵌入另一个页面，并在嵌入状态和切换后的全屏状态之间无缝转换，从而解决上述源的问题。</p>
         </div>

mobile/network.html

@@ -19,7 +19,7 @@ <h2>Well-deployed technologies</h2>
         </div>
 
         <div data-feature="Cross-domain Requests">
-          <p>By default, browsers do not allow to make request across different domains (or more specifically, across different origins, a combination of the protocol, domain and port) from a single Web page; this rule protects the user from having a Web site abusing their credentials and stealing their data on another Web site. Sites can opt-out of that rule by making use of the <a data-featureid="cors">Cross-Origin Resource Sharing</a> (CORS) mechanism, opening up much wider cooperation across Web applications and services. Note the W3C version of the CORS specification does not reflect current implementations and will be obsoleted. The CORS mechanism is now a core part of the on-going <a href="https://fetch.spec.whatwg.org/">Fetch specification</a> in the WHATWG.</p>
+          <p>By default, browsers do not allow to make request across different domains (or more specifically, across different origins, a combination of the protocol, domain and port) from a single Web page; this rule protects the user from having a Web site abusing their credentials and stealing their data on another Web site. Sites can opt-out of that rule by making use of the <a data-featureid="fetch/cors">Cross-Origin Resource Sharing</a> (CORS) mechanism, opening up much wider cooperation across Web applications and services.</p>
         </div>
 
         <div data-feature="Server-pushed Requests">

mobile/network.zh.html

@@ -19,7 +19,7 @@ <h2>广泛部署的技术</h2>
         </div>
 
         <div data-feature="跨域请求">
-          <p>默认情况下，浏览器不允许在单个网页上的不同域名（或者更具体地说，不同源，包括协议、域名和端口的组合）之间进行请求；这个规则保护用户，使用户们不会被一个网站滥用他们的证书并窃取他们在另一个网站上的数据。站点可以通过使用<a data-featureid="cors">跨源资源共享</a>（Cross-Origin Resource Sharing，CORS）机制来选择退出该规则，从而在 Web 应用和服务之间开展更广泛的合作。请注意 CORS 规范的 W3C 版本并不能反映现有的实现，并将被废弃。CORS 机制现在是 WHATWG <a href="https://fetch.spec.whatwg.org/">Fetch 规范</a>的核心部分。</p>
+          <p>默认情况下，浏览器不允许在单个网页上的不同域名（或者更具体地说，不同源，包括协议、域名和端口的组合）之间进行请求；这个规则保护用户，使用户们不会被一个网站滥用他们的证书并窃取他们在另一个网站上的数据。站点可以通过使用<a data-featureid="fetch/cors">跨源资源共享</a>（Cross-Origin Resource Sharing，CORS）机制来选择退出该规则，从而在 Web 应用和服务之间开展更广泛的合作。</p>
         </div>
 
         <div data-feature="服务器推送请求">