<?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: The time element (and microformats)</title>
	<atom:link href="http://html5doctor.com/the-time-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com/the-time-element/</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Mon, 21 May 2012 10:47:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Ryan Benson</title>
		<link>http://html5doctor.com/the-time-element/#comment-21236</link>
		<dc:creator>Ryan Benson</dc:creator>
		<pubDate>Wed, 11 Jan 2012 21:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-21236</guid>
		<description>When the datetime attribute is used, is it essentially ignored by assistive technology? That is if a screen reader hit
I am going swimming at 8pm on my birthday. Will a screen reader announce &quot;I am going swimming at 8pm on my birthday&quot; or &quot;I am going swimming at 2009 dash 11dash 13T20:00plus00colon00&quot;? Since users cannot get the latest version of assistive technology always, what versions were tested?</description>
		<content:encoded><![CDATA[<p>When the datetime attribute is used, is it essentially ignored by assistive technology? That is if a screen reader hit<br />
I am going swimming at 8pm on my birthday. Will a screen reader announce &#8220;I am going swimming at 8pm on my birthday&#8221; or &#8220;I am going swimming at 2009 dash 11dash 13T20:00plus00colon00&#8243;? Since users cannot get the latest version of assistive technology always, what versions were tested?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to use HTML5 in your client work right now &#124; HTML5 Doctor &#171; Codingbird</title>
		<link>http://html5doctor.com/the-time-element/#comment-21155</link>
		<dc:creator>How to use HTML5 in your client work right now &#124; HTML5 Doctor &#171; Codingbird</dc:creator>
		<pubDate>Wed, 28 Dec 2011 04:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-21155</guid>
		<description>[...] elements such as &lt;time&gt; to add semantics that will be interpreted by leading [...]</description>
		<content:encoded><![CDATA[<p>[...] elements such as &lt;time&gt; to add semantics that will be interpreted by leading [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oli Studholme</title>
		<link>http://html5doctor.com/the-time-element/#comment-18526</link>
		<dc:creator>Oli Studholme</dc:creator>
		<pubDate>Mon, 14 Nov 2011 11:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18526</guid>
		<description>@Andy Mabbett — it’s a good thing we’re lazy huh ;)

@Trond Husø — the &lt;code&gt;datetime&lt;/code&gt; attribute can contain dates &lt;strong&gt;and/or&lt;/strong&gt; times. No need to overly complicate things with three attributes when one will do.

@anon — for more information see our article &lt;a href=&quot;http://html5doctor.com/time-and-data-element/&quot; rel=&quot;nofollow&quot;&gt;Goodbye time, datetime, and pubdate. Hello data and value.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>@Andy Mabbett — it’s a good thing we’re lazy huh ;)</p>
<p>@Trond Husø — the <code>datetime</code> attribute can contain dates <strong>and/or</strong> times. No need to overly complicate things with three attributes when one will do.</p>
<p>@anon — for more information see our article <a href="http://html5doctor.com/time-and-data-element/" rel="nofollow">Goodbye time, datetime, and pubdate. Hello data and value.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://html5doctor.com/the-time-element/#comment-18520</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Mon, 14 Nov 2011 00:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18520</guid>
		<description>It looks like the change to the spec to replace the time element with the data element has been reverted for now due to not having all the proper committee review:

http://lists.w3.org/Archives/Public/public-html/2011Nov/0098.html</description>
		<content:encoded><![CDATA[<p>It looks like the change to the spec to replace the time element with the data element has been reverted for now due to not having all the proper committee review:</p>
<p><a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0098.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2011Nov/0098.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://html5doctor.com/the-time-element/#comment-18372</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Mon, 07 Nov 2011 20:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18372</guid>
		<description>Trond,

you&#039;re mixing semantics - the time tag only makes sense if the only content within it is a representation of the attribute, ie. it really is a data item albeit with one of far greater relevance than many of the others. I think the big problem with time is, as you suggest, that the attribute must be mandatory with the representation as a backwardly compatible option. Formatting would default to the long format for the browser&#039;s locale. Not sure whether this should be overridable by CSS - what would be the other use cases? or a format attribute. That kind of specification would have made implementation a lot more straightforward and that would have encouraged adoption.</description>
		<content:encoded><![CDATA[<p>Trond,</p>
<p>you&#8217;re mixing semantics &#8211; the time tag only makes sense if the only content within it is a representation of the attribute, ie. it really is a data item albeit with one of far greater relevance than many of the others. I think the big problem with time is, as you suggest, that the attribute must be mandatory with the representation as a backwardly compatible option. Formatting would default to the long format for the browser&#8217;s locale. Not sure whether this should be overridable by CSS &#8211; what would be the other use cases? or a format attribute. That kind of specification would have made implementation a lot more straightforward and that would have encouraged adoption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trond Husø</title>
		<link>http://html5doctor.com/the-time-element/#comment-18371</link>
		<dc:creator>Trond Husø</dc:creator>
		<pubDate>Mon, 07 Nov 2011 20:26:12 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18371</guid>
		<description>eh, the tags above was &lt;datetime&gt; where it should be mandatory with one attribute.

&lt;code&gt;
&lt;datetime datetime=&quot;2009-11-13T20:00+00:00&quot;&gt; Starting at 8pm on November 13, 2009&lt;/datetime&gt;
&lt;datetime date=&quot;2009-11-13&quot;&gt; November 13, 2009&lt;/datetime&gt;
&lt;datetime time=&quot;20:00&quot;&gt; Starting at 8pm&lt;/datetime&gt;
&lt;datetime date=&quot;2009-11-13&quot; Time=&quot;20:00&quot;&gt; Starting at 8pm on November 13, 2009&lt;/datetime&gt;
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>eh, the tags above was &lt;datetime&gt; where it should be mandatory with one attribute.</p>
<p><code><br />
&lt;datetime datetime="2009-11-13T20:00+00:00"&gt; Starting at 8pm on November 13, 2009&lt;/datetime&gt;<br />
&lt;datetime date="2009-11-13"&gt; November 13, 2009&lt;/datetime&gt;<br />
&lt;datetime time="20:00"&gt; Starting at 8pm&lt;/datetime&gt;<br />
&lt;datetime date="2009-11-13" Time="20:00"&gt; Starting at 8pm on November 13, 2009&lt;/datetime&gt;<br />
</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trond Husø</title>
		<link>http://html5doctor.com/the-time-element/#comment-18370</link>
		<dc:creator>Trond Husø</dc:creator>
		<pubDate>Mon, 07 Nov 2011 20:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18370</guid>
		<description>Bruce. Looking at the tag it seems turned around. And your example does shows that not make sense at all.

I mean:
In the example you are showing a date inside a time tag. 
In the next example you are doing the same, saying that the value in the tag is a datetime.

It would be better if the tag was 
and that atleast one attribute was required either date or time
so that you could do:
Starting at 8pm
Starting at 8pm on November 13, 2009
Starting at 8pm on November 13, 2009

I do believe it is a need for a time/date tag in HTML. It is a welcoming suggestion for articles / CRM systems where you can both mark up the time and date of the article, and also time and date of any update. 

Keep up the good work with the spec.

Trond</description>
		<content:encoded><![CDATA[<p>Bruce. Looking at the tag it seems turned around. And your example does shows that not make sense at all.</p>
<p>I mean:<br />
In the example you are showing a date inside a time tag.<br />
In the next example you are doing the same, saying that the value in the tag is a datetime.</p>
<p>It would be better if the tag was<br />
and that atleast one attribute was required either date or time<br />
so that you could do:<br />
Starting at 8pm<br />
Starting at 8pm on November 13, 2009<br />
Starting at 8pm on November 13, 2009</p>
<p>I do believe it is a need for a time/date tag in HTML. It is a welcoming suggestion for articles / CRM systems where you can both mark up the time and date of the article, and also time and date of any update. </p>
<p>Keep up the good work with the spec.</p>
<p>Trond</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Mabbett</title>
		<link>http://html5doctor.com/the-time-element/#comment-18251</link>
		<dc:creator>Andy Mabbett</dc:creator>
		<pubDate>Sat, 29 Oct 2011 15:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18251</guid>
		<description>@Oli - I&#039;d take a backup of older articles before you change them, if I were you, just in case this gets arbitrarily flipped back again ;-) 

@Bruce - One use-case or a datetime attribute in IMG might be for discoverability: &quot;find me all images from 1 April 2009&quot;; but Charlie&#039;s point about EXIF has merit.</description>
		<content:encoded><![CDATA[<p>@Oli &#8211; I&#8217;d take a backup of older articles before you change them, if I were you, just in case this gets arbitrarily flipped back again ;-) </p>
<p>@Bruce &#8211; One use-case or a datetime attribute in IMG might be for discoverability: &#8220;find me all images from 1 April 2009&#8243;; but Charlie&#8217;s point about EXIF has merit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oli Studholme</title>
		<link>http://html5doctor.com/the-time-element/#comment-18249</link>
		<dc:creator>Oli Studholme</dc:creator>
		<pubDate>Sat, 29 Oct 2011 06:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18249</guid>
		<description>@Tyler — yup, more background here: &lt;a href=&quot;http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240&quot; rel=&quot;nofollow&quot;&gt;Bug 13240 - Consider replacing &lt;code&gt;&lt;time&gt;&lt;/code&gt; with &lt;code&gt;&lt;data&gt;&lt;/code&gt;&lt;/a&gt;. We’ll publish something on it and update affected articles asap. In the meantime, all hail &lt;a href=&quot;http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-data-element&quot; title=&quot;4.6 Text-level semantics &#8212; HTML Standard&quot; rel=&quot;nofollow&quot;&gt;the &lt;code&gt;&lt;data&gt;&lt;/code&gt; element&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>@Tyler — yup, more background here: <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240" rel="nofollow">Bug 13240 &#8211; Consider replacing <code>&lt;time&gt;</code> with <code>&lt;data&gt;</code></a>. We’ll publish something on it and update affected articles asap. In the meantime, all hail <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-data-element" title="4.6 Text-level semantics &#8212; HTML Standard" rel="nofollow">the <code>&lt;data&gt;</code> element</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler</title>
		<link>http://html5doctor.com/the-time-element/#comment-18248</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Sat, 29 Oct 2011 06:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1293#comment-18248</guid>
		<description>Did this element just get dropped per this? http://html5.org/tools/web-apps-tracker?from=6782&amp;to=6783</description>
		<content:encoded><![CDATA[<p>Did this element just get dropped per this? <a href="http://html5.org/tools/web-apps-tracker?from=6782&#038;to=6783" rel="nofollow">http://html5.org/tools/web-apps-tracker?from=6782&#038;to=6783</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

