<?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"
	>
<channel>
	<title>Comments on: SCORM for Dummies</title>
	<atom:link href="http://cogdogblog.com/2004/05/26/scorm-for/feed/" rel="self" type="application/rss+xml" />
	<link>http://cogdogblog.com/2004/05/26/scorm-for/</link>
	<description>Alan Levine's blog space for barking about instructional technology</description>
	<pubDate>Sat, 22 Nov 2008 06:00:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Scott Leslie</title>
		<link>http://cogdogblog.com/2004/05/26/scorm-for/#comment-591</link>
		<dc:creator>Scott Leslie</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/scorm-for-dummies/#comment-591</guid>
		<description>Alan, the irony of this presentation you point to is that it is by Phil Dodds of the ADL, who obviously knows a great deal about SCORM, and yet I would rate this one of the worst 'dummies' guides I've ever seen; poorly laid out, still crammed with acronyms, and using phrasing, like the one you point to in your last paragraph, that speak of seemingly non-existance SCORM-compliant LMS and just end up confusing the reader.



The document is entirely accurate, just not very clear. SCORM really does two things. It makes learning content portable between systems that recognize the manner in which SCORM content packages work. And secondly it means that the systems between which that learning content can be moved can all launch and track how users move through the content in exactly the same way. What it meant is that publishers could no longer get away with selling you digital content that wouldn't play properly in your CMS/LMS, and CMS/LMS vendors couldn't get away with selling you a system that trapped you into forever using that system because your content was stuck in its proprietary format.



It is important in providing a stable format for electronic learning content and thus creating the basis for a content marketplace to emerge, but at the same time it is dead boring stuff, and IMHO gets more attention than is its due simply for having a cool-sounding acronym (never underestimate the power of a cool-sounding acronym!)



Cheers, Scott.
</description>
		<content:encoded><![CDATA[<p>Alan, the irony of this presentation you point to is that it is by Phil Dodds of the ADL, who obviously knows a great deal about SCORM, and yet I would rate this one of the worst &#8216;dummies&#8217; guides I&#8217;ve ever seen; poorly laid out, still crammed with acronyms, and using phrasing, like the one you point to in your last paragraph, that speak of seemingly non-existance SCORM-compliant LMS and just end up confusing the reader.</p>
<p>The document is entirely accurate, just not very clear. SCORM really does two things. It makes learning content portable between systems that recognize the manner in which SCORM content packages work. And secondly it means that the systems between which that learning content can be moved can all launch and track how users move through the content in exactly the same way. What it meant is that publishers could no longer get away with selling you digital content that wouldn&#8217;t play properly in your CMS/LMS, and CMS/LMS vendors couldn&#8217;t get away with selling you a system that trapped you into forever using that system because your content was stuck in its proprietary format.</p>
<p>It is important in providing a stable format for electronic learning content and thus creating the basis for a content marketplace to emerge, but at the same time it is dead boring stuff, and IMHO gets more attention than is its due simply for having a cool-sounding acronym (never underestimate the power of a cool-sounding acronym!)</p>
<p>Cheers, Scott.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
