Ian Hickson wrote: >> For example, it uses the term "protocol"; RFC 3986 uses the term >> "scheme." >> The HTML 5 specification should use the terminology defined by the >> current standard for URIs. > This section is just specifying (for the first time) an API that > has been implemented in browsers for a decade and a half at least.
An old browser happily treated http host:80 as different from host, this certainly needs a clarification (= old browser got this wrong). But there is no <hostport> in STD 66 outside of appendix D.2 about obsolete terminology. > only the attribute names use these old terms <hostport> is no attribute name, it's simple to avoid it. If you are hunting obscure syntax details in STD 66 tackle the question of port = *DIGIT, WTH is an empty port introduced by a colon ? More interesting, what's an empty fragment introduced by "#" ? Various browsers interpret this as "top of file" for text/html. > refering to URLs as defined by HTML5 instead of URIs or IRIs, > but that's another issue Frank -- <http://omniplex.blogspot.com/2008/07/html5-asinine-selfish.html>
