Re: [w3c/WebPlatformWG] CFC: Make previous versions of HTML and XHTML obsoleteCFC: Make previous versions of HTML and XHTML obsolete (#86)

In practice, the main effect of marking a Recommendation obsolete is to provide a forward link to the latest version. All Recommendations are "stable" in the sense that they don't change unless significant errata are found, especially when there are subsequent versions that accept changes.

In my mind, this is similar to IETF RFCs, which indicate in their header which documents a new document obsoletes, and which documents supersede it. In HTML, it is true that HTML 5.1 is intended to supersede HTML 5.0 and we should make specs in that way. It doesn't make apps that target HTML 5.0 invalid, it doesn't change the IPR considerations for HTML 5.0, it just means the document will have a forward link that says, essentially, "This document was superseded by this later one".

In that sense, it seems strange to me that we should argue that HTML 4 was superseded but HTML 5.0 has not been.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/WebPlatformWG/issues/86#issuecomment-316373490