New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't www.w3.org/TR/html5/ point to the "Latest version of HTML5"? #1089

Closed
SelenIT opened this Issue Nov 28, 2017 · 6 comments

Comments

Projects
None yet
6 participants
@SelenIT

SelenIT commented Nov 28, 2017

Currently, the URL https://www.w3.org/TR/html5/ points to the HTML5.0 Rec from 2014. Since the URL follows the same pattern as https://www.w3.org/TR/html4/, which points to the "Latest version of HTML 4", people can conclude that it's the "Latest version of HTML5". There is no signs in the HTML5.0 spec itself (except the "Latest Version of HTML" link in the header) that it's in fact the outdated snapshot, so many people still believe it's the actual HTML standard and continue to link to it.

Shouldn't this URL actually display the content of the "Latest version of HTML5" (currently it's HTML5.1 2nd Edition, soon it would be HTML5.2), and shouldn't the 2014 snapshot have the dedicated URL like https://www.w3.org/TR/html50/ instead, following the URL pattern of other HTML5 snapshots (5.1, 5.2, etc.)?

@SelenIT SelenIT changed the title from Shouldn't www.w3.org/TR/html5/ point to the "latest version of HTML5"? to Shouldn't www.w3.org/TR/html5/ point to the "Latest version of HTML5"? Nov 28, 2017

@plehegar

This comment has been minimized.

Show comment
Hide comment
@plehegar

plehegar Dec 5, 2017

Member

2 possibilities:

  1. /TR/html5/ is the URL of HTML 5.0, so we keep things as-is.
  2. /TR/html5/ was an unfortunately pick. So, we could rename the current /TR/html5 to be /TR/html50 and then have /TR/html5/ to be an alias of /TR/html/ ?

Preferences?

cc @deniak

Member

plehegar commented Dec 5, 2017

2 possibilities:

  1. /TR/html5/ is the URL of HTML 5.0, so we keep things as-is.
  2. /TR/html5/ was an unfortunately pick. So, we could rename the current /TR/html5 to be /TR/html50 and then have /TR/html5/ to be an alias of /TR/html/ ?

Preferences?

cc @deniak

@johnfoliot

This comment has been minimized.

Show comment
Hide comment
@johnfoliot

johnfoliot Dec 5, 2017

johnfoliot commented Dec 5, 2017

@SelenIT

This comment has been minimized.

Show comment
Hide comment
@SelenIT

SelenIT Dec 6, 2017

I strongly prefer option 2, too.

Many existing resources link to /TR/html5 as the relevant HTML(5) spec, so it would be great if it automagically starts to point to the latest published version.

SelenIT commented Dec 6, 2017

I strongly prefer option 2, too.

Many existing resources link to /TR/html5 as the relevant HTML(5) spec, so it would be great if it automagically starts to point to the latest published version.

@edent

This comment has been minimized.

Show comment
Hide comment
@edent

edent Dec 6, 2017

Contributor

Option 2, I agree. Cool URls don't change, and all that 😀

Contributor

edent commented Dec 6, 2017

Option 2, I agree. Cool URls don't change, and all that 😀

@LJWatson

This comment has been minimized.

Show comment
Hide comment
@LJWatson

LJWatson Dec 6, 2017

Collaborator

Agree that option 2 is the better choice. It's consistent with subsequent versions (/html51, /html52 etc.)

Collaborator

LJWatson commented Dec 6, 2017

Agree that option 2 is the better choice. It's consistent with subsequent versions (/html51, /html52 etc.)

@deniak

This comment has been minimized.

Show comment
Hide comment
@deniak

deniak Dec 7, 2017

Member

Links updated

Member

deniak commented Dec 7, 2017

Links updated

@deniak deniak closed this Dec 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment