<?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: SCORM 2004</title>
	<atom:link href="http://log.reflectivesurface.com/2004/02/06/scorm-2004/feed/" rel="self" type="application/rss+xml" />
	<link>http://log.reflectivesurface.com/2004/02/06/scorm-2004/</link>
	<description>Still powered by a contradiction in terms</description>
	<pubDate>Tue, 06 Jan 2009 03:40:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ronaldo</title>
		<link>http://log.reflectivesurface.com/2004/02/06/scorm-2004/comment-page-1/#comment-255</link>
		<dc:creator>Ronaldo</dc:creator>
		<pubDate>Wed, 03 Nov 2004 23:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://log.reflectivesurface.com/2004/02/06/scorm-2004/#comment-255</guid>
		<description>John, I elaborated on the issue of existing flaws in the standard on my firstpost about the subject which you can find searching for "SCORM" in the site's search function. To sum it, I consider the reliance on client-side programming to be the biggest flaw in the standard.

About what's needed to make it useful at large, I believe SCORM must allow for server-side processing by way of a common API. It's impossible, for example, to create a database of questions for random use in a course unless you put it in the client, in case which the database can't be expanded without republishing the course. Also, since the answers are also on the client, any users that knows how to use the view source command in the browser can see the answers -- unless they're obscured somehow. That's but one example of the problems with the current standard. There are many other issues involving security, transactions, tests, and thegeneral flexibility of the standard that makes it less useful than itcould be.

I hope this helped.
</description>
		<content:encoded><![CDATA[<p>John, I elaborated on the issue of existing flaws in the standard on my firstpost about the subject which you can find searching for &#8220;SCORM&#8221; in the site&#8217;s search function. To sum it, I consider the reliance on client-side programming to be the biggest flaw in the standard.</p>
<p>About what&#8217;s needed to make it useful at large, I believe SCORM must allow for server-side processing by way of a common API. It&#8217;s impossible, for example, to create a database of questions for random use in a course unless you put it in the client, in case which the database can&#8217;t be expanded without republishing the course. Also, since the answers are also on the client, any users that knows how to use the view source command in the browser can see the answers &#8212; unless they&#8217;re obscured somehow. That&#8217;s but one example of the problems with the current standard. There are many other issues involving security, transactions, tests, and thegeneral flexibility of the standard that makes it less useful than itcould be.</p>
<p>I hope this helped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Benson</title>
		<link>http://log.reflectivesurface.com/2004/02/06/scorm-2004/comment-page-1/#comment-254</link>
		<dc:creator>John Benson</dc:creator>
		<pubDate>Tue, 02 Nov 2004 15:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://log.reflectivesurface.com/2004/02/06/scorm-2004/#comment-254</guid>
		<description>Can you expand on "The standards existing flaws are still there, and much of whats needed to really make it useful at large (at least, in my opinion) are far from being implemented."

that is, what are the existing flaws?

what do you mean by "...what's needed to really make it useful at large"

thank you

John</description>
		<content:encoded><![CDATA[<p>Can you expand on &#8220;The standards existing flaws are still there, and much of whats needed to really make it useful at large (at least, in my opinion) are far from being implemented.&#8221;</p>
<p>that is, what are the existing flaws?</p>
<p>what do you mean by &#8220;&#8230;what&#8217;s needed to really make it useful at large&#8221;</p>
<p>thank you</p>
<p>John</p>
]]></content:encoded>
	</item>
</channel>
</rss>
