Http-equiv VS name meta tags

[rincewind]

Hi,
Is there a difference in <meta http-equiv="description" content="relevant description"> or
<meta name="description" content="relevant description">
and the keyword equivalents? and if there is what are the advantages/disadvantages over the other?
Thanks

[Charles]

As a part of the behind the scenes communication between a browser and a server, servers generate an HTTP response header for each document. This header is prepended to each document but the server can request just the header. That way the browser can check the header against the version already in the cache and decide if it really needs to request a whole new document. Some servers allow you to use the "http-equiv" attribute with the META element to directly manipulate the HTTP response header. See http://www.w3.org/TR/html4/struct/global.html#h-7.4.4 for more on the META element.

The "http-equiv" should only be used for stuff that the browser needs to know. Things like the character encoding, the expiration date and such. For keywords you want to use the "name" attribute though you might want to use the Dublin Core with that. (http://dublincore.org/).

Far more important than key words, though, are properly marked up headings. Us things like <h4>What the Giant Said</h4>.

[rincewind]

so just to be clear
<meta http-equiv="description" content="relevant description"> is incorrect and will not work correctly with search engines and
<meta name="description" content="relevant description">
should be used?
Thanks.
Considering header tags are so important how can you incorporate this into a style sheet where the headings are at the moment also links and defined in the style sheet as
a.newshead {FONT-FAMILY: arial, helvetica, sans-serif; font-size: 9pt; COLOR: rgb(255,137,21); TEXT-DECORATION: none}
Thanks again.