W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: meta/@name=description

From: Chris Cressman <chris@chriscressman.com>
Date: Wed, 19 Aug 2009 12:57:21 -0400
Message-ID: <3d99ba250908190957j6baf7ab0ob2e911be7589f8d8@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "public-html@w3.org" <public-html@w3.org>
> 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.

> <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
would pursue this within the microformats community.

[1] http://wiki.whatwg.org/wiki/RelExtensions
[2] http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-link-element

Chris
--
Chris Cressman
http://chriscressman.com
Received on Thursday, 20 August 2009 15:30:05 UTC

This archive was generated by hypermail 2.3.1 : Friday, 10 October 2014 16:24:51 UTC