From 3d10320a49ca9cef533d3ca3b2b5ca7677076b36 Mon Sep 17 00:00:00 2001 From: Jake Archibald Date: Tue, 13 Sep 2016 17:01:58 +0100 Subject: [PATCH] Updating links, removing old redirects, removing remaining references to web component framework. --- CONTRIBUTING.md | 4 ++-- README.md | 10 ++-------- docs/index.bs | 4 ++-- docs/v1/index.bs | 2 +- explainer.md | 6 +++--- implementation_considerations.md | 2 +- index.html | 9 --------- spec/service_worker/index.html | 10 ---------- 8 files changed, 11 insertions(+), 36 deletions(-) delete mode 100644 index.html delete mode 100644 spec/service_worker/index.html diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 868ff4f5..e861caeb 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,13 +2,13 @@ ## Spec and API development -For the nitty-gritty of the API, the [draft W3C specification](https://w3c.github.io/ServiceWorker/spec/service_worker/) is authoritative. For implementers and developers who seek a more stable version, [Service Workers 1](https://w3c.github.io/ServiceWorker/spec/service_worker_1/) is a right document with which the contributors only focus on fixing bugs and resolving compatibility issues. +For the nitty-gritty of the API, the [draft W3C specification](https://w3c.github.io/ServiceWorker/) is authoritative. For implementers and developers who seek a more stable version, [Service Workers 1](https://w3c.github.io/ServiceWorker/v1/) is a right document with which the contributors only focus on fixing bugs and resolving compatibility issues. Spec development happens via [issues in this repository](https://github.com/w3c/ServiceWorker/issues). For general discussion, please use the [public-webapps@w3.org mailing list](http://lists.w3.org/Archives/Public/public-webapps/) with a `Subject:` prefix of `[service-workers]`. Updates to the spec must reference [resolved issues marked `needs spec`](https://github.com/w3c/ServiceWorker/issues?q=is%3Aclosed+label%3A%22needs+spec%22). -To make edits to the design, please send pull requests against the Nightly spec on the master branch. We use [bikeshed](https://github.com/tabatkins/bikeshed). So, change `spec/service_worker/index.bs` and submit it with the corresponding bikesheded `index.html`. +To make edits to the design, please send pull requests against the Nightly spec on the master branch. We use [bikeshed](https://github.com/tabatkins/bikeshed). So, change `docs/index.bs` and submit it with the corresponding bikesheded `index.html`. Contributions to this repository are intended to become part of Recommendation-track documents governed by the [W3C Patent Policy](http://www.w3.org/Consortium/Patent-Policy-20040205/) and diff --git a/README.md b/README.md index f98e38aa..48260a25 100644 --- a/README.md +++ b/README.md @@ -10,19 +10,13 @@ To understand the design and how you might build apps with service workers, see ## Spec and API development -For the nitty-gritty of the API, the [draft W3C specification](https://w3c.github.io/ServiceWorker/spec/service_worker/) is authoritative. For implementers and developers who seek a more stable version, [Service Workers 1](https://w3c.github.io/ServiceWorker/spec/service_worker_1/) is a right document with which the contributors only focus on fixing bugs and resolving compatibility issues. +For the nitty-gritty of the API, the [draft W3C specification](https://w3c.github.io/ServiceWorker/) is authoritative. For implementers and developers who seek a more stable version, [Service Workers 1](https://w3c.github.io/ServiceWorker/) is a right document with which the contributors only focus on fixing bugs and resolving compatibility issues. Spec development happens via [issues in this repository](https://github.com/w3c/ServiceWorker/issues). For general discussion, please use the [public-webapps@w3.org mailing list](http://lists.w3.org/Archives/Public/public-webapps/) with a `Subject:` prefix of `[service-workers]`. Updates to the spec must reference [resolved issues marked `needs spec`](https://github.com/w3c/ServiceWorker/issues?q=is%3Aclosed+label%3A%22needs+spec%22). -To edit the spec locally, you’ll need a copy of [the Web Components-based framework which it is built with](https://github.com/slightlyoff/web-spec-framework). To fetch it, clone the repo and run: - -```sh -git submodule update --init --recursive -``` - -To make edits to the design, please send pull requests against the Nightly spec on the master branch. We use [bikeshed](https://github.com/tabatkins/bikeshed). So, change `spec/service_worker/index.bs` and submit it with the corresponding bikesheded `index.html`. +To make edits to the design, please send pull requests against the Nightly spec on the master branch. We use [bikeshed](https://github.com/tabatkins/bikeshed). So, change `docs/index.bs` and submit it with the corresponding bikesheded `index.html`. ## Examples diff --git a/docs/index.bs b/docs/index.bs index b707048f..132d3f0c 100644 --- a/docs/index.bs +++ b/docs/index.bs @@ -1,7 +1,7 @@ 
 Title: Service Workers Nightly
 Status: ED
-ED: https://w3c.github.io/ServiceWorker/spec/service_worker/
+ED: https://w3c.github.io/ServiceWorker/
 TR: https://www.w3.org/TR/service-workers/
 Shortname: service-workers
 Level:
@@ -11,7 +11,7 @@ Editor: Jake Archibald, Google, jakearchibald@chromium.org
 Editor: Marijn Kruisselbrink, Google, mek@chromium.org
 Repository: w3c/ServiceWorker
 Group: webplatform
-Status Text: This is a living document addressing new features including foreign fetch and header-based installation, etc. Readers need to be aware that this specification includes unstable features. Implementers interested in implementing this specification should refer to the latest TR of Service Workers 1 instead.
+Status Text: This is a living document addressing new features including foreign fetch and header-based installation, etc. Readers need to be aware that this specification includes unstable features. Implementers interested in implementing this specification should refer to the latest TR of Service Workers 1 instead.
 Abstract: This specification describes a method that enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of web applications while offline.
 Abstract:
 Abstract: The core of this system is an event-driven Web Worker, which responds to events dispatched from documents and other sources. A system for managing installation, versions, and upgrades is provided.
diff --git a/docs/v1/index.bs b/docs/v1/index.bs
index 44d180b2..a770fce4 100644
--- a/docs/v1/index.bs
+++ b/docs/v1/index.bs
@@ -1,7 +1,7 @@
 
 Title: Service Workers 1
 Status: ED
-ED: https://w3c.github.io/ServiceWorker/spec/service_worker_1/
+ED: https://w3c.github.io/ServiceWorker/v1/
 TR: https://www.w3.org/TR/service-workers/
 Shortname: service-workers
 Level: 1
diff --git a/explainer.md b/explainer.md
index e345369d..f33b3a22 100644
--- a/explainer.md
+++ b/explainer.md
@@ -90,7 +90,7 @@ If you refresh the document, it’ll be under the service worker’s control. Yo
 
 If you shift+reload a document it’ll always load without a controller, which is handy for testing quick CSS & JS changes.
 
-Documents tend to live their whole life with a particular service worker, or none at all. However, a service worker can call `self.skipWaiting()` ([spec](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#service-worker-global-scope-skipwaiting)) to do an immediate takeover of all pages within scope.
+Documents tend to live their whole life with a particular service worker, or none at all. However, a service worker can call `self.skipWaiting()` ([spec](https://w3c.github.io/ServiceWorker/#service-worker-global-scope-skipwaiting)) to do an immediate takeover of all pages within scope.
 
 ## Network intercepting
 
@@ -187,7 +187,7 @@ The easiest way at the moment is to close & reopen the tab (cmd+w, then cmd+shif
 
 ## The cache
 
-service worker comes with a [caching API](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#cache-objects), letting you create stores of responses keyed by request.
+service worker comes with a [caching API](https://slightlyoff.github.io/ServiceWorker/#cache-objects), letting you create stores of responses keyed by request.
 
 ```js
 self.addEventListener('install', function(event) {
@@ -215,7 +215,7 @@ self.addEventListener('fetch', function(event) {
 
 Matching within the cache is similar to the browser cache. Method, URL and vary headers are taken into account, but freshness headers are ignored. Things are only removed from caches when you remove them.
 
-You can add individual items to the cache with `cache.put(request, response)`, including ones you’ve created yourself. You can also control matching, [discounting things](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#cache-query-options-dictionary) such as query string, methods, and vary headers.
+You can add individual items to the cache with `cache.put(request, response)`, including ones you’ve created yourself. You can also control matching, [discounting things](https://slightlyoff.github.io/ServiceWorker/#cache-query-options-dictionary) such as query string, methods, and vary headers.
 
 ## Other service worker–related specifications
 
diff --git a/implementation_considerations.md b/implementation_considerations.md
index 5bd7ed33..e5b8fbf7 100644
--- a/implementation_considerations.md
+++ b/implementation_considerations.md
@@ -6,7 +6,7 @@ Or
 
 So you’ve got a browser engine, are looking into this whole "Service Workers" thing and have some questions. Take heart, dear reader! Your friendly spec designers/authors are here to answer your (anticipated) questions. Want more answers? [File a bug](issues) and tag it `implementation-concern`.
 
-This doc looks first at key concepts then outlines the [areas of helpful built-in ambiguity ](https://w3c.github.io/ServiceWorker/spec/service_worker/) that provide opportunities to go fast. Each opportunity includes a list of strategies that implementations might explore to improve service worker performance.
+This doc looks first at key concepts then outlines the [areas of helpful built-in ambiguity ](https://w3c.github.io/ServiceWorker/) that provide opportunities to go fast. Each opportunity includes a list of strategies that implementations might explore to improve service worker performance.
 
 ## Key concepts
 
diff --git a/index.html b/index.html
deleted file mode 100644
index 2029db74..00000000
--- a/index.html
+++ /dev/null
@@ -1,9 +0,0 @@
-
-
-
-Moved…
-
-
-
Moved to
-https://w3c.github.io/ServiceWorker/docs/
-
diff --git a/spec/service_worker/index.html b/spec/service_worker/index.html
deleted file mode 100644
index 37f4a3be..00000000
--- a/spec/service_worker/index.html
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-  
-
-Moved…
-
-
-
Moved to
-https://w3c.github.io/ServiceWorker/docs/
-
\ No newline at end of file