A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Fork tracking"

From WHATWG Wiki
Jump to: navigation, search
(Confusion Somewhat Mitigated)
(Flesh out)
Line 4: Line 4:
 
== Confusion Mitigated ==
 
== Confusion Mitigated ==
  
* Fullscreen
+
* Fullscreen: https://fullscreen.spec.whatwg.org/
** http://www.w3.org/TR/fullscreen/
+
** Forked to http://www.w3.org/TR/fullscreen/
 
** Status: discontinued as a NOTE. ED URL (http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html) redirects
 
** Status: discontinued as a NOTE. ED URL (http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html) redirects
  
 
== Confusion Somewhat Mitigated ==
 
== Confusion Somewhat Mitigated ==
  
* URL
+
* URL: https://url.spec.whatwg.org/
** http://www.w3.org/TR/url/ plus various aliases and older versions
+
** Forked to http://www.w3.org/TR/url/ plus various aliases and older versions
 
** Status: has a reasonable red disclaimer, but still exists.
 
** Status: has a reasonable red disclaimer, but still exists.
 
** Also, https://w3ctag.github.io/url/ exists without the disclaimer.
 
** Also, https://w3ctag.github.io/url/ exists without the disclaimer.
* Streams
+
* Streams: https://streams.spec.whatwg.org/
** http://www.w3.org/TR/streams-api/
+
** Forked to http://www.w3.org/TR/streams-api/
 
** Status: mostly gutted, with a reasonable red disclaimer.
 
** Status: mostly gutted, with a reasonable red disclaimer.
  
 
== Confusion Persists ==
 
== Confusion Persists ==
  
* CORS
+
* Fetch: https://fetch.spec.whatwg.org/
** http://www.w3.org/TR/cors/
+
** Obsolete subsections published as http://www.w3.org/TR/cors/
** Status: still exists as an outdated specification with no warning, causing confusion. Obsoleted by the Fetch standard.
+
** Status: still exists as an outdated specification with no warning, causing confusion.
* DOM
+
* DOM: https://dom.spec.whatwg.org/
** http://www.w3.org/TR/dom/
+
** Forked to http://www.w3.org/TR/dom/
** Status: still exists as an outdated snapshot with no warning, causing confusion. And has a weird rename too.
+
** Status: still exists as an outdated snapshot with no warning, causing confusion. And has a weird rename ("DOM4") too.
* Encoding
+
* Encoding: https://encoding.spec.whatwg.org/
** http://www.w3.org/TR/encoding/
+
** Forked to http://www.w3.org/TR/encoding/
 
** Status: still exists as an outdated snapshot with no warning, causing confusion
 
** Status: still exists as an outdated snapshot with no warning, causing confusion
* Notifications
+
* Notifications: https://notifications.spec.whatwg.org/
** http://www.w3.org/TR/notifications/
+
** Forked to http://www.w3.org/TR/notifications/
 
** Status: still exists as an outdated snapshot with no warning, causing confusion. The spec model has diverged significantly in the meantime, and the outdated version is actively wrong, not just incomplete.
 
** Status: still exists as an outdated snapshot with no warning, causing confusion. The spec model has diverged significantly in the meantime, and the outdated version is actively wrong, not just incomplete.
* XMLHttpRequest
+
* XMLHttpRequest: https://xhr.spec.whatwg.org/
** http://www.w3.org/TR/XMLHttpRequest/
+
** Forked to http://www.w3.org/TR/XMLHttpRequest/
** http://www.w3.org/TR/XMLHttpRequest2/
+
** Forked to http://www.w3.org/TR/XMLHttpRequest2/
** Status: Although XHR "level 2" has been discontinued as a NOTE, XHR "level 1" continues to exist as an outdated snapshot with no warning, causing confusion. The spec is not properly layered on top of the Fetch Standard, either, which means it fails to integrate with the rest of the platform (e.g. it is not intercepted by service workers).
+
** Status: Although XHR "level 2" has been discontinued as a NOTE, XHR "level 1" continues to exist as an outdated snapshot with no warning, causing confusion. The spec is not properly layered on top of the Fetch Standard, either, which means it fails to integrate with the rest of the platform (e.g. it is not intercepted by service workers, according to the fork).
* HTML
+
* HTML: https://html.spec.whatwg.org/multipage/
** http://www.w3.org/TR/html5/ is an outdated fork of a subset of HTML; very bad.
+
** Forked to http://www.w3.org/TR/html5/ as an outdated fork of a subset frozen in 2013.
** http://www.w3.org/TR/html51/ attempts to copy-and-paste HTML and then apply forked patches on top, but the scripts are wonky, leading to lots of errors.
+
** Forked to http://www.w3.org/TR/html51/ as an outdated fork of a subset frozen in 2015.
** Subsets of HTML split out into outdated forks:
+
** Forked to https://w3c.github.io/html/ as an outdated fork of a subset frozen in early 2016 (see [https://annevankesteren.nl/2016/01/film-at-11 blog post]).
 +
** In general all of these attempt to copy-and-paste HTML and then apply forked patches on top, but the scripts are wonky, leading to lots of errors.
 +
** Subsets of HTML split out into other outdated forks, none with appropriate warnings:
 
*** http://www.w3.org/TR/webstorage/
 
*** http://www.w3.org/TR/webstorage/
 
*** http://www.w3.org/TR/workers/
 
*** http://www.w3.org/TR/workers/

Revision as of 16:11, 21 January 2016

This page exists to document the status of the outdated forks of various WHATWG specifications, and any progress toward clarifying their out-of-dateness.


Confusion Mitigated

Confusion Somewhat Mitigated

Confusion Persists