canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
The term URL has a technical meaning that doesn't match the HTML5 spec. Even
though the spec points this out, some find this confusing or objectionable.
Suggestions for alternate terms include "Web Address" or "HREF"
(following IRIbis) or "HURL" (for HTML URL) or anything that doesn't conflict
with IETF specs in this area. Such a change would be cosmetic but it would not
be obviously harmful and would apparently remove objections.
(Note: The description above is a slight rewording of the description that was originally submitted for the bugzilla bug related to this issue - http://www.w3.org/Bugs/Public/show_bug.cgi?id=7392)
Add notes (no markup allowed, URIs get automatically hyperlinked):
this is a dup of ISSUE-56, no?
[MikeSmith]: during 2009-09-10 telcon we resolved that this issue is not a duplication of issue 56 and so it should be kept open
One related Bugzilla entry: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8116
Comments added to Bug 8116 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8116 ) and bug 7392 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=7392 ) which should also be linked here.
If the "real solution" is to get the entire standards community to adopt the term "URL" as it is used by the HTML5 specifications, there is an opportunity to do so, since most people look to the IETF specifications for definitions of the terminology.
[plh]: closed without prejudice due to lack of change proposals
[rubys]: closed without prejudice