<?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: &quot;Which part of SCORM should I implement in my LMS?&quot;</title>
	<atom:link href="http://scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/feed/" rel="self" type="application/rss+xml" />
	<link>http://scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/</link>
	<description>We make SCORM easy</description>
	<lastBuildDate>Tue, 22 May 2012 11:50:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: SCORM &#187; Drupal, SCORM, and why The Partridge Family was wrong</title>
		<link>http://scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/comment-page-1/#comment-351</link>
		<dc:creator>SCORM &#187; Drupal, SCORM, and why The Partridge Family was wrong</dc:creator>
		<pubDate>Wed, 02 Sep 2009 19:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://beta.scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/#comment-351</guid>
		<description>[...] but SCORM really suffers from inconsistent implementations. If you&#8217;re going to implement part of SCORM, please do the industry as a whole a favor&#8230; finish [...]</description>
		<content:encoded><![CDATA[<p>[...] but SCORM really suffers from inconsistent implementations. If you&#8217;re going to implement part of SCORM, please do the industry as a whole a favor&#8230; finish [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Martin</title>
		<link>http://scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/comment-page-1/#comment-350</link>
		<dc:creator>Tim Martin</dc:creator>
		<pubDate>Mon, 22 Dec 2008 18:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/#comment-350</guid>
		<description>Right on, Dave.  I couldn&#039;t agree more.  For someone who will have control over both the content and the LMS (as you do in Articulate Online), SCORM is more hassle than help.  You guys are able to do things in reporting data that SCORM simply doesn&#039;t allow for.  (Detailed interaction reporting is a great example of this, and, something I &lt;a HREF=&quot;http://www.scorm.com/scormblog/2008/12/joe-smith-answered-question-1-with-b.aspx&quot; REL=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;posted&lt;/a&gt; on a few weeks ago.&lt;br/&gt;&lt;br/&gt;The benefit of SCORM comes when you deliver content to another LMS provider and need to know that certain aspects of LMS functionality are globally available.  (Obviously, at Articulate, you&#039;re well informed in that regard, given your broad success in delivering content in so many LMS&#039;s.)&lt;br/&gt;&lt;br/&gt;Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Right on, Dave.  I couldn&#8217;t agree more.  For someone who will have control over both the content and the LMS (as you do in Articulate Online), SCORM is more hassle than help.  You guys are able to do things in reporting data that SCORM simply doesn&#8217;t allow for.  (Detailed interaction reporting is a great example of this, and, something I <a HREF="http://www.scorm.com/scormblog/2008/12/joe-smith-answered-question-1-with-b.aspx" REL="nofollow" >posted</a> on a few weeks ago.</p>
<p>The benefit of SCORM comes when you deliver content to another LMS provider and need to know that certain aspects of LMS functionality are globally available.  (Obviously, at Articulate, you&#8217;re well informed in that regard, given your broad success in delivering content in so many LMS&#8217;s.)</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/comment-page-1/#comment-349</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 19 Dec 2008 23:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.scorm.com/blog/2008/12/which-part-of-scorm-should-i-implement-in-my-lms/#comment-349</guid>
		<description>Interesting post.&lt;br/&gt;&lt;br/&gt;When we originally built Articulate Online we built it only for our products and to support only our products, but we still used SCORM 1.2 for reporting thinking it wouldn&#039;t be that bad.  We ran into a host of problems with some of the limitations of SCORM, like the limit on the number of characters for Essay questions, characters that aren&#039;t supported, which made things difficult because with Articulate Online we had a goal of having really rich reports, which was difficult to support using SCORM as our communication mechanism.&lt;br/&gt;&lt;br/&gt;We eventually switched our new products to use our own new proprietary communication method that wasn&#039;t bound by the limitations of SCORM.  As a QA person I hated the idea of changing our communication mechanism in our new products because hey, we spent so much time getting the SCORM approach to work, but after all was said and done, our own proprietary communication method caused way less headaches, and had way less bugs.&lt;br/&gt;&lt;br/&gt;Don&#039;t get me wrong, SCORM is great, but it would have worked better for us to just begin with our own communication method.&lt;br/&gt;&lt;br/&gt;But I have to totally agree with this:&lt;br/&gt;&quot;Your content vendors will hate you!&quot;&lt;br/&gt;&lt;br/&gt;I can&#039;t count how many times I have heard from people that content created with our software doesn&#039;t work in their &quot;in house&quot; developed LMS and the problem ends up being some half assed implementation.</description>
		<content:encoded><![CDATA[<p>Interesting post.</p>
<p>When we originally built Articulate Online we built it only for our products and to support only our products, but we still used SCORM 1.2 for reporting thinking it wouldn&#8217;t be that bad.  We ran into a host of problems with some of the limitations of SCORM, like the limit on the number of characters for Essay questions, characters that aren&#8217;t supported, which made things difficult because with Articulate Online we had a goal of having really rich reports, which was difficult to support using SCORM as our communication mechanism.</p>
<p>We eventually switched our new products to use our own new proprietary communication method that wasn&#8217;t bound by the limitations of SCORM.  As a QA person I hated the idea of changing our communication mechanism in our new products because hey, we spent so much time getting the SCORM approach to work, but after all was said and done, our own proprietary communication method caused way less headaches, and had way less bugs.</p>
<p>Don&#8217;t get me wrong, SCORM is great, but it would have worked better for us to just begin with our own communication method.</p>
<p>But I have to totally agree with this:<br />&#8220;Your content vendors will hate you!&#8221;</p>
<p>I can&#8217;t count how many times I have heard from people that content created with our software doesn&#8217;t work in their &#8220;in house&#8221; developed LMS and the problem ends up being some half assed implementation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

