- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 10 Dec 2008 21:59:33 +1100
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, "Atom Syntax" <atom-syntax@imc.org>, www-tag@w3.org, "HTML WG" <public-html@w3.org>
On 10/12/2008, at 9:52 PM, Anne van Kesteren wrote: > On Wed, 10 Dec 2008 11:29:02 +0100, Mark Nottingham <mnot@mnot.net> > wrote: >> On 10/12/2008, at 9:04 PM, Anne van Kesteren wrote: >> >>> Then again, it seems the HTTP Link you define is not very much in >>> line with HTML5 <link>, <a>, <area> anyway. >> >> Can you give a little more detail? > > Skimming through the drafts for a few minutes I find at least these: > > In HTML5 the tokens are not URIs and are not really URI-references > either because they have to be case-insensitively matched (the HTML5 > specification is currently wrong on this). (http://www.iana.org/assignments/relation/stylesheet > and stylesheet are therefore not equal either.) The registered tokens are effectively tokens, and can be considered case-insensitive (see the notes on use in HTML4). > In HTML5 people can simply provisionally register a new token by > putting it on a wiki page. The token does not have to be a URI. > (Though it could be a string that is also a URI.) See the discussion with Phil. > In HTML5 there is no rev "link-param" because (non-academic) studies > have shown that people do not really know how to use it. See current discussion about deprecating it. > In HTML5 media, hreflang, and sizes (just for <link>) also influence > the relationship. Your draft does not have these "link-param"s. Other extensions are allowed; again, see the appendix about use in HTML. -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 10 December 2008 11:00:15 UTC