- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 19 Aug 2009 19:06:28 +0200
- To: Chris Cressman <chris@chriscressman.com>
- CC: "public-html@w3.org" <public-html@w3.org>
Chris Cressman wrote: >> A drawback is that it uses hidden metadata, and, even worse, is likely to >> duplicate information from the page. It seems what's needed is to markup the >> page so that a consumer can actually locate the description inside the page. >> >> One way to do that would be a link relation, for instance: >> >> <link rel="description" href="#desc"/> > > The WHATWG Wiki has a RelExtensions page [1] where anyone can add > additional rel values. However, I don't think your example is an > appropriate use of the LINK element in HTML 5 [2]. The LINK element > would need to be redefined (or clarified) to allow linking to a > fragment within the current document. If "link" currently disallows in-document links then that is clearly a bug; they are widely used and interoperable. >> <div id="desc"> >> <h2>Abstract</h2> >> <p> >> ...description text... >> </p> >> </div> > > I agree that moving the meta description into the body of the page is > a good idea. I also think the idea of using a reserved id name could > work. However, I wouldn't expect HTML 5 to adopt this. Instead, I I didn't intend the ID to be reserved. > would pursue this within the microformats community. > ... ...and that's exactly I wouldn't want a microformat. BR, Julian
Received on Wednesday, 19 August 2009 17:07:12 UTC