From 08dbaf913976783ae9bfb9a1054d9f1e6eeb7d06 Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 26 Feb 2020 15:25:14 +0100
Subject: [PATCH] Editorial: remove schemeless origin group

Closes #77.
---
 storage.bs | 20 ++++----------------
 1 file changed, 4 insertions(+), 16 deletions(-)

diff --git a/storage.bs b/storage.bs
index 79497f6..c1b213f 100644
--- a/storage.bs
+++ b/storage.bs
@@ -79,18 +79,6 @@ Promise.all([
 <p>This specification uses terminology from the DOM, HTML, IDL, Permissions API, and URL Standards.
 [[DOM]] [[HTML]] [[WEBIDL]] [[PERMISSIONS]] [[URL]]
 
-A <dfn>schemeless origin group</dfn> is a group of one of the following:
-
-<ul>
- <li>Identical <a lt="opaque origin">opaque origins</a>.
- <li><a lt="tuple origin">Tuple origins</a> whose <a for=origin>host</a> is identical and not a
- <a for=/>domain</a>.
- <li><a lt="tuple origin">Tuple origins</a> whose <a for=origin>host</a> is a <a for=/>domain</a> of
- which the <a href="https://publicsuffix.org/list/">registrable domain</a> is identical.</li>
-</ul>
-
-<p class="note">This definition will move to a more suitable location eventually.
-
 
 
 <h2 id=infrastructure>Infrastructure</h2>
@@ -183,10 +171,10 @@ indications of "popularity".
 <h2 id=ui-guidelines>User Interface Guidelines</h2>
 
 User agents should not distinguish between network storage and <a>site storage</a> in their user
-interface. Instead user agents should offer users the ability to remove all storage for a given
-<a>schemeless origin group</a>. This ensures to some extent that network storage cannot be used to
-revive <a>site storage</a>. This also reduces the amount users need to know about the different ways
-in which a <a>schemeless origin group</a> can store data.
+interface. Instead user agents should offer users the ability to remove all storage for each group
+of <a>schemelessly same site</a> <a for=/>origins</a>. This ensures to some extent that network
+storage cannot be used to revive <a>site storage</a>. This also reduces the amount users need to
+know about the different ways in which sites can store data.
 <!-- To some extent, since HTTP ETag... And also, permissions/credentials, maybe? -->
 
 Credentials storage should be separated as it might contain data the user might not be able to