<?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: ISO 8601 Date Validation That Doesn&#8217;t Suck</title>
	<atom:link href="http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/</link>
	<description>Santa Barbara Web Design and Web Development Blog on the web world and other randoms</description>
	<lastBuildDate>Mon, 06 Feb 2012 20:31:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: parse this type of date format in java? - Stack Overflow</title>
		<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/comment-page-1/#comment-6691</link>
		<dc:creator>parse this type of date format in java? - Stack Overflow</dc:creator>
		<pubDate>Tue, 08 Feb 2011 15:17:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.pelagodesign.com/blog/?p=448#comment-6691</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Another answer, since you seem to be focused on simply tearing the String apart (not a good idea, IMHO.) Let&#039;s assume the string is valid ISO8601. Can you assume it will always be in the form you cite, or is it just valid 8601? If the latter, you have to cope with a bunch of scenarios as these guys did. [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://www.pelagodesign.com/blog/wp-content/plugins/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] Another answer, since you seem to be focused on simply tearing the String apart (not a good idea, IMHO.) Let&#39;s assume the string is valid ISO8601. Can you assume it will always be in the form you cite, or is it just valid 8601? If the latter, you have to cope with a bunch of scenarios as these guys did. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron</title>
		<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/comment-page-1/#comment-6505</link>
		<dc:creator>Cameron</dc:creator>
		<pubDate>Fri, 19 Feb 2010 16:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.pelagodesign.com/blog/?p=448#comment-6505</guid>
		<description>BobM,

You are indeed correct. The date you had is a valid ISO 8601 date, and should have passed. My original regex didn&#039;t support fractional decimals, as Intervals didn&#039;t require that level of precision. I&#039;ve updated this post and the regex to add support for this. Thank you for finding this bug and please let me know if you find anything else.

Cameron</description>
		<content:encoded><![CDATA[<p>BobM,</p>
<p>You are indeed correct. The date you had is a valid ISO 8601 date, and should have passed. My original regex didn&#8217;t support fractional decimals, as Intervals didn&#8217;t require that level of precision. I&#8217;ve updated this post and the regex to add support for this. Thank you for finding this bug and please let me know if you find anything else.</p>
<p>Cameron</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BobM</title>
		<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/comment-page-1/#comment-6503</link>
		<dc:creator>BobM</dc:creator>
		<pubDate>Fri, 19 Feb 2010 00:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pelagodesign.com/blog/?p=448#comment-6503</guid>
		<description>This did not work for me on the string 2010-02-18T16:23:48.541-06:00   I tested using the regex tester at http://www.fileformat.info/tool/regex.htm which is good for testing how Java will process a regex.  The date came to me as a xs:date (xml date) passed through a web service.  I think this may well not be a truly ISO 8601 date format, but it is what java developers will often see when working with xml.  If this is not 8601, what is wrong with it?

Thanks,
Bob</description>
		<content:encoded><![CDATA[<p>This did not work for me on the string 2010-02-18T16:23:48.541-06:00   I tested using the regex tester at <a href="http://www.fileformat.info/tool/regex.htm" rel="nofollow">http://www.fileformat.info/tool/regex.htm</a> which is good for testing how Java will process a regex.  The date came to me as a xs:date (xml date) passed through a web service.  I think this may well not be a truly ISO 8601 date format, but it is what java developers will often see when working with xml.  If this is not 8601, what is wrong with it?</p>
<p>Thanks,<br />
Bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron Brooks</title>
		<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/comment-page-1/#comment-6350</link>
		<dc:creator>Cameron Brooks</dc:creator>
		<pubDate>Mon, 10 Aug 2009 16:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pelagodesign.com/blog/?p=448#comment-6350</guid>
		<description>You can use that like any other regular expression to match a string. We do use it in production in our API for validating the format of dates passed to us, and it&#039;s not particularly taxing on the system (though I can&#039;t give you an exact estimation of the processing power it uses; obviously it&#039;s more taxing than, say, matching a phone number via regex). For more information on using Perl Compatible Regular Expressions in PHP, check out http://us.php.net/manual/en/book.pcre.php, and to learn more about the preg_match function specifically, check out http://us.php.net/preg_match.

Cameron</description>
		<content:encoded><![CDATA[<p>You can use that like any other regular expression to match a string. We do use it in production in our API for validating the format of dates passed to us, and it&#8217;s not particularly taxing on the system (though I can&#8217;t give you an exact estimation of the processing power it uses; obviously it&#8217;s more taxing than, say, matching a phone number via regex). For more information on using Perl Compatible Regular Expressions in PHP, check out <a href="http://us.php.net/manual/en/book.pcre.php" rel="nofollow">http://us.php.net/manual/en/book.pcre.php</a>, and to learn more about the preg_match function specifically, check out <a href="http://us.php.net/preg_match" rel="nofollow">http://us.php.net/preg_match</a>.</p>
<p>Cameron</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Gearon</title>
		<link>http://www.pelagodesign.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/comment-page-1/#comment-6345</link>
		<dc:creator>Dennis Gearon</dc:creator>
		<pubDate>Sat, 08 Aug 2009 02:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.pelagodesign.com/blog/?p=448#comment-6345</guid>
		<description>How do you use this? Have you used it in production? How much processing does a regex like that use?</description>
		<content:encoded><![CDATA[<p>How do you use this? Have you used it in production? How much processing does a regex like that use?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

