<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: From the Top: The Meta Element</title>
	<atom:link href="http://multicelldesign.com/2006/03/meta-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://multicelldesign.com/2006/03/meta-element/</link>
	<description>shokunin kishitsu</description>
	<lastBuildDate>Mon, 28 Nov 2011 19:43:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Daryl A. Szady</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-118</link>
		<dc:creator>Daryl A. Szady</dc:creator>
		<pubDate>Sat, 08 Apr 2006 21:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-118</guid>
		<description>Sorry I didn&#039;t reply in the correct form before:
&lt;code&gt;&lt;meta name=&quot;date&quot; content=&quot;2006-04-06T05:41:27.178Z&quot; /&gt;&lt;/code&gt;
&lt;code&gt;&lt;meta name=&quot;modified&quot; content=&quot;2006-04-06T08:04:44.73Z&quot; /&gt;&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Sorry I didn&#8217;t reply in the correct form before:<br />
<code>&lt;meta name="date" content="2006-04-06T05:41:27.178Z" /&gt;</code><br />
<code>&lt;meta name="modified" content="2006-04-06T08:04:44.73Z" /&gt;</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daryl A. Szady</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-117</link>
		<dc:creator>Daryl A. Szady</dc:creator>
		<pubDate>Tue, 28 Mar 2006 23:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-117</guid>
		<description>I use these two meta elements:

UTC, so there isn&#039;t any ambiguity when it was created or modified.</description>
		<content:encoded><![CDATA[<p>I use these two meta elements:</p>
<p>UTC, so there isn&#8217;t any ambiguity when it was created or modified.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy Olsson</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-116</link>
		<dc:creator>Tommy Olsson</dc:creator>
		<pubDate>Wed, 15 Mar 2006 11:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-116</guid>
		<description>It&#039;s worth mentioning that you cannot actually change the &lt;em&gt;content type&lt;/em&gt; using an HTTP equivalent. You may specify the character encoding, though.

In other words, you can&#039;t use
&lt;code&gt;&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;application/xhtml+xml; charset=utf-8&quot;/&gt;&lt;/code&gt;
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.</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth mentioning that you cannot actually change the <em>content type</em> using an HTTP equivalent. You may specify the character encoding, though.</p>
<p>In other words, you can&#8217;t use<br />
<code>&lt;meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/&gt;</code><br />
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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Wellock</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-115</link>
		<dc:creator>Robert Wellock</dc:creator>
		<pubDate>Tue, 14 Mar 2006 15:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-115</guid>
		<description>Usually the thing that is overlooked by most authors regarding the META is the default Scripting and Style Sheet Language may be defined there.</description>
		<content:encoded><![CDATA[<p>Usually the thing that is overlooked by most authors regarding the META is the default Scripting and Style Sheet Language may be defined there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Dawson</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-114</link>
		<dc:creator>Karl Dawson</dc:creator>
		<pubDate>Mon, 13 Mar 2006 20:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-114</guid>
		<description>Hi Thierry,

I would use the name of the person who &lt;em&gt;owns&lt;/em&gt; the document rather than the developer&#039;s name for the author &#8212; 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 &#8212; a page about cats is bound to mention that in the &lt;code&gt;description&lt;/code&gt; 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 &lt;code&gt;author&lt;/code&gt; meta tag would provide a means to identify someone &lt;em&gt;responsible&lt;/em&gt; for the page and hence if a problem was reported with the content &#8212; 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</description>
		<content:encoded><![CDATA[<p>Hi Thierry,</p>
<p>I would use the name of the person who <em>owns</em> the document rather than the developer&#8217;s name for the author &#8212; 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.</p>
<p>The content and the web page (document) are naturally linked when it comes to keywords and description &#8212; 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.</p>
<p>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 &#8212; 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.</p>
<p>Regards, Karl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-113</link>
		<dc:creator>Thierry</dc:creator>
		<pubDate>Mon, 13 Mar 2006 19:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-113</guid>
		<description>Nicely written, but I find these two confusing:
&lt;blockquote&gt;The meta element provides web document authors the ability to provide information about the document rather than the content itself. &lt;/blockquote&gt;
&lt;blockquote&gt;Author and copyright meta tags are probably useful, especially for articles and tutorials..&lt;/blockquote&gt;
So are they related to the document itself or its content? What name should appear in there? The name of the author of the document (designer/developer) or the name of the person who actually wrote the content (article, tutorial, whatever)?</description>
		<content:encoded><![CDATA[<p>Nicely written, but I find these two confusing:</p>
<blockquote><p>The meta element provides web document authors the ability to provide information about the document rather than the content itself. </p></blockquote>
<blockquote><p>Author and copyright meta tags are probably useful, especially for articles and tutorials..</p></blockquote>
<p>So are they related to the document itself or its content? What name should appear in there? The name of the author of the document (designer/developer) or the name of the person who actually wrote the content (article, tutorial, whatever)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://multicelldesign.com/2006/03/meta-element/comment-page-1/#comment-112</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Mon, 13 Mar 2006 16:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/2006/03/13/from-the-top-the-meta-element/#comment-112</guid>
		<description>As usual, Karl, this is pretty thorough and well written. Regarding dates, I&#039;ve read somewhere that the only way to write a date fully accepted in all corners of the world is year/month/day, numerically: 2006-03-13. Good stuff.</description>
		<content:encoded><![CDATA[<p>As usual, Karl, this is pretty thorough and well written. Regarding dates, I&#8217;ve read somewhere that the only way to write a date fully accepted in all corners of the world is year/month/day, numerically: 2006-03-13. Good stuff.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

