<?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: Step 54 &#8211; Error Handling?</title>
	<atom:link href="http://www.vsscorm.net/2010/07/13/step-54-error-handling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vsscorm.net/2010/07/13/step-54-error-handling/</link>
	<description>A Very Simple SCORM Interface</description>
	<lastBuildDate>Sun, 02 Oct 2011 18:07:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Step 60 &#8211; Supported Data Elements &#124; VSSCORM</title>
		<link>http://www.vsscorm.net/2010/07/13/step-54-error-handling/comment-page-1/#comment-324</link>
		<dc:creator>Step 60 &#8211; Supported Data Elements &#124; VSSCORM</dc:creator>
		<pubDate>Tue, 06 Sep 2011 15:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsscorm.net/?p=1507#comment-324</guid>
		<description>[...] One of the things that has caught me out in a couple of recent cases is that the SCORM standard makes SCO developers rely on error codes to determine whether or not certain elements are supported. I describe one specific example in an earlier post &#8211; Step 54 &#8211; Error Handling. [...]</description>
		<content:encoded><![CDATA[<p>[...] One of the things that has caught me out in a couple of recent cases is that the SCORM standard makes SCO developers rely on error codes to determine whether or not certain elements are supported. I describe one specific example in an earlier post &#8211; Step 54 &#8211; Error Handling. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

