Comments on: From the Top: The Meta Element http://www.thatstandardsguy.co.uk/2006/03/meta-element/ a web developer with standards Mon, 29 Mar 2010 11:42:21 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: Daryl A. Szady http://www.thatstandardsguy.co.uk/2006/03/meta-element/comment-page-1/#comment-179 Daryl A. Szady Sat, 08 Apr 2006 21:04:02 +0000 http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-179 Sorry I didn't reply in the correct form before: <code><meta name="date" content="2006-04-06T05:41:27.178Z" /></code> <code><meta name="modified" content="2006-04-06T08:04:44.73Z" /></code> Sorry I didn’t reply in the correct form before:
<meta name="date" content="2006-04-06T05:41:27.178Z" />
<meta name="modified" content="2006-04-06T08:04:44.73Z" />

]]> By: Daryl A. Szady http://www.thatstandardsguy.co.uk/2006/03/meta-element/comment-page-1/#comment-163 Daryl A. Szady Tue, 28 Mar 2006 23:12:55 +0000 http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-163 I use these two meta elements: UTC, so there isn't any ambiguity when it was created or modified. I use these two meta elements:

UTC, so there isn’t any ambiguity when it was created or modified.

]]> By: Tommy Olsson http://www.thatstandardsguy.co.uk/2006/03/meta-element/comment-page-1/#comment-156 Tommy Olsson Wed, 15 Mar 2006 11:09:26 +0000 http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-156 It's worth mentioning that you cannot actually change the <em>content type</em> using an HTTP equivalent. You may specify the character encoding, though. In other words, you can't use <code><meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/></code> to serve a document as XHTML. A user agent needs this information before the HTTP body is received, in order to select a suitable parser. It needs to go in a true HTTP header. It’s worth mentioning that you cannot actually change the content type using an HTTP equivalent. You may specify the character encoding, though.

In other words, you can’t use
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/>
to serve a document as XHTML. A user agent needs this information before the HTTP body is received, in order to select a suitable parser. It needs to go in a true HTTP header.

]]> By: Robert Wellock http://www.thatstandardsguy.co.uk/2006/03/meta-element/comment-page-1/#comment-154 Robert Wellock Tue, 14 Mar 2006 15:11:46 +0000 http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-154 Usually the thing that is overlooked by most authors regarding the META is the default Scripting and Style Sheet Language may be defined there. Usually the thing that is overlooked by most authors regarding the META is the default Scripting and Style Sheet Language may be defined there.

]]> By: Karl Dawson http://www.thatstandardsguy.co.uk/2006/03/meta-element/comment-page-1/#comment-153 Karl Dawson Mon, 13 Mar 2006 20:40:31 +0000 http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-153 Hi Thierry, I would use the name of the person who <em>owns</em> the document rather than the developer's name for the author — especially if you (as a developer) had created a website for someone else. With self-publishing to blogs like this one then the author is most likely the developer also. The content and the web page (document) are naturally linked when it comes to keywords and description — a page about cats is bound to mention that in the <code>description</code> meta tag but meta data can be more abstract than that case when you consider embedding time stamps etc. In a content management system (CMS) environment within a large organisation the <code>author</code> meta tag would provide a means to identify someone <em>responsible</em> for the page and hence if a problem was reported with the content — broken link, spelling error etc. then the support team (who are most likely not responsible for content) would know who to contact to correct the page. The detail, or content, on the page is irrelevant in this example. Regards, Karl Hi Thierry,

I would use the name of the person who owns the document rather than the developer’s name for the author — especially if you (as a developer) had created a website for someone else. With self-publishing to blogs like this one then the author is most likely the developer also.

The content and the web page (document) are naturally linked when it comes to keywords and description — a page about cats is bound to mention that in the description meta tag but meta data can be more abstract than that case when you consider embedding time stamps etc.

In a content management system (CMS) environment within a large organisation the author meta tag would provide a means to identify someone responsible for the page and hence if a problem was reported with the content — broken link, spelling error etc. then the support team (who are most likely not responsible for content) would know who to contact to correct the page. The detail, or content, on the page is irrelevant in this example.

Regards, Karl

]]>