From 2303f31368ef97c3dea4ffbfd03ccb017ede65da Mon Sep 17 00:00:00 2001 From: Paul Meyer Date: Thu, 5 Jul 2018 14:48:10 -0400 Subject: [PATCH 1/2] Update "WICG" -> "W3C" --- index.src.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/index.src.html b/index.src.html index fd83e49..7ffdb55 100644 --- a/index.src.html +++ b/index.src.html @@ -1,9 +1,9 @@

Reporting API

-Status: CG-DRAFT
-ED: https://wicg.github.io/reporting/
+Status: w3c/CG-DRAFT
+ED: https://w3c.github.io/reporting/
 Shortname: reporting
-Group: wicg
+Group: w3c
 Editor: Douglas Creager 103120, Google Inc., dcreager@google.com
 Editor: Ilya Grigorik 56102, Google Inc., igrigorik@google.comm
 Editor: Mike West 56384, Google Inc., mkwst@google.com
@@ -15,9 +15,9 @@ 

Reporting API

reports in a consistent manner. Level: 1 Indent: 2 -Version History: https://github.com/wicg/reporting/commits/master/index.src.html +Version History: https://github.com/w3c/reporting/commits/master/index.src.html Boilerplate: omit conformance, omit feedback-header -!Participate: File an issue (open issues) +!Participate: File an issue (open issues) Markup Shorthands: css off, markdown on
@@ -1403,7 +1403,7 @@ 

Network Leakage

one network to be sent while the user is on another network, even if they don't explicitly open the page from which the report was sent. - ISSUE(WICG/BackgroundSync#107): Consider mitigations. For example, we could + ISSUE(W3C/BackgroundSync#107): Consider mitigations. For example, we could drop reports if we change from one network to another.

Clock Skew

From 282d9cefaf0c23c3e73b86dd4cad0a286c48a506 Mon Sep 17 00:00:00 2001 From: Paul Meyer Date: Fri, 6 Jul 2018 11:35:46 -0400 Subject: [PATCH 2/2] addressed comments --- index.src.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.src.html b/index.src.html index 7ffdb55..07b5a7b 100644 --- a/index.src.html +++ b/index.src.html @@ -1,9 +1,9 @@

Reporting API