This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7577 - meta/@name=descriptions vs invisible metadata
Summary: meta/@name=descriptions vs invisible metadata
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-09-11 11:57 UTC by Julian Reschke
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:


Description Julian Reschke 2009-09-11 11:57:15 UTC
HTML5 defines meta/@name=description, and this is a good thing, as it is used in the wild, and actually used by search engines.

However, it is a case of invisible metadata, and furthermore forces authors to repeat text that already appears somewhere else on the page.

A link relation or a new container element <description> could address this.

See <> for a proposal of a link relation.
Comment 1 Anne 2009-09-11 14:17:22 UTC
A link relation can easily be developed outside HTML5.
Comment 2 Julian Reschke 2009-09-11 14:26:49 UTC
That argument applies to lots of stuff which is in HTML5 currently as well.
Comment 3 Anne 2009-09-11 14:29:15 UTC
That does not seem like a good reason to do more of it.
Comment 4 Maciej Stachowiak 2010-03-14 14:50:58 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.