- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 12 Dec 2006 00:24:27 +0000 (UTC)
On Tue, 12 Dec 2006, Karl Dubost wrote: > Le 12 d?c. 2006 ? 07:19, Ian Hickson a ?crit : > > > I'm not sure what the solution to this problem is. > > > > Me neither. Suggestions welcome. > > For example for hcard, you could do: > > <link rel="hcard" href="http://www.w3.org/2006/vcard/ns"/> > <link rel="hcard" href="http://www.w3.org/2006/03/hcard"/> I don't really understand how that would solve the problem; could you elaborate? > I proposed to modify the link element as such: > > ================================== > 3.8.4. The link element > > Metadata element. > > Contexts in which this element may be used: > Where strictly inline-level content is allowed. > =================================== > > Rationale: > So people can add it in a web form, and then do in situ editing. Metadata can > be near the content when needed. > > I would also propose the same for the meta element. Unfortunately in both cases we don't really have any choice; for back compat, <link> and <meta> elements that aren't in the <head> must be moved to the <head> by the parser. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 11 December 2006 16:24:27 UTC