Quantcast
Channel: vTraining Room » LMS Tips and Tricks
Viewing all articles
Browse latest Browse all 12

Response: Why the Tin Can API will not replace SCORM

0
0

I have heard an argument made that it’s just not happening.  Here is an example of just such an argument.  I agree that Tin Can API may not replace SCORM content that already exists (companies and course vendors that have libraries of hundreds or thousands of SCORM courses).   However, the Experience API will be the standard moving forward.  That is, once folks have an opportunity to use it, and share the cool aid. Seriously though, if you look at how people are implementing learning solutions today, the xAPI is not something people will give up once they have had an opportunity to deploy it in their programs.  They will demand more solutions based on it, or additional ideas on usage, instead of craving more standardized rules.   The Experience API 1.0 already solves many of the challenges and limitations people have had using SCORM.  I know it can be tough to not look at the past and think how much better things were in the good old days.  But, we as an industry are moving on…For instructional designers and LMS administrators, perhaps times were not all that great in the past.  Sure a SCORM SCO is a more clearly defined package, but I would be a rich man if I had a penny for every time I gave the advice “Don’t use the newer SCORM2004 standard, the decade older publishing option will work much better on your LMS”.  Client response: “Really?”   Also, I wish I could show you the black eyes I have gotten standing in the middle of a battle between content provider and Learning Management system when things go sideways with a SCORM package.  I can’t believe I am the only one out [...]

The post Response: Why the Tin Can API will not replace SCORM appeared first on vTraining Room.


Viewing all articles
Browse latest Browse all 12

Latest Images

Trending Articles





Latest Images