<?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: Learning objects</title>
	<atom:link href="http://www.daveswhiteboard.com/archives/260/feed" rel="self" type="application/rss+xml" />
	<link>http://www.daveswhiteboard.com/archives/260?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=learning-objects</link>
	<description>Dave Ferguson&#039;s interests, ideas, notions, tangents</description>
	<lastBuildDate>Sat, 17 Jul 2010 15:10:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Dave</title>
		<link>http://www.daveswhiteboard.com/archives/260/comment-page-1#comment-7764</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 18 Apr 2008 18:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.daveswhiteboard.com/archives/260#comment-7764</guid>
		<description>Philip, thanks for being a voice of reason.  (I do rant recreationally at times.)

I have no problem with portability between LMSs, as far as it goes; that&#039;s just packaging.  

You&#039;re certainly right about the stylistic differences, let alone the technological ones -- and often clients in their first efforts have a hard time picturing how all the storyboards and assets add up to a course.  So it&#039;s sometimes hard to communicate the value of graphics (illustrations, text with graphic elements) that are integrated into an overall design scheme.</description>
		<content:encoded><![CDATA[<p>Philip, thanks for being a voice of reason.  (I do rant recreationally at times.)</p>
<p>I have no problem with portability between LMSs, as far as it goes; that&#8217;s just packaging.  </p>
<p>You&#8217;re certainly right about the stylistic differences, let alone the technological ones &#8212; and often clients in their first efforts have a hard time picturing how all the storyboards and assets add up to a course.  So it&#8217;s sometimes hard to communicate the value of graphics (illustrations, text with graphic elements) that are integrated into an overall design scheme.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philip</title>
		<link>http://www.daveswhiteboard.com/archives/260/comment-page-1#comment-7763</link>
		<dc:creator>philip</dc:creator>
		<pubDate>Fri, 18 Apr 2008 17:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.daveswhiteboard.com/archives/260#comment-7763</guid>
		<description>yeah, i think one of the dangers of working with SCORM -- at least the way SCORM developers *want* you to work with it -- is that you spend way too much time focusing on the technology end of your elearning course and not on the content and instructional value. 

the best courses are highly customized... SCORM&#039;s &#039;repurposing&#039; ideals are commendable, but usually lead to somewhat generic courses.

Also (as far as I know), SCORM doesn&#039;t address stylistic and file format differences between SCOs; what if one was designed with a bright blue HTML/CSS scheme while the other uses Captivate with a deep red scheme?  The visual and functional disconnect would certainly have a negative affect on the course&#039;s effectiveness. To my knowledge, SCORM doesn&#039;t address this issue except to say &quot;make your stuff as boring and plain as possible.&quot;

Because of all this, I only use SCORM to handle course communication issues (ensuring portability between LMSs) and don&#039;t worry about reusability with other SCOs.</description>
		<content:encoded><![CDATA[<p>yeah, i think one of the dangers of working with SCORM &#8212; at least the way SCORM developers *want* you to work with it &#8212; is that you spend way too much time focusing on the technology end of your elearning course and not on the content and instructional value. </p>
<p>the best courses are highly customized&#8230; SCORM&#8217;s &#8216;repurposing&#8217; ideals are commendable, but usually lead to somewhat generic courses.</p>
<p>Also (as far as I know), SCORM doesn&#8217;t address stylistic and file format differences between SCOs; what if one was designed with a bright blue HTML/CSS scheme while the other uses Captivate with a deep red scheme?  The visual and functional disconnect would certainly have a negative affect on the course&#8217;s effectiveness. To my knowledge, SCORM doesn&#8217;t address this issue except to say &#8220;make your stuff as boring and plain as possible.&#8221;</p>
<p>Because of all this, I only use SCORM to handle course communication issues (ensuring portability between LMSs) and don&#8217;t worry about reusability with other SCOs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
