For quite some time now the learning community has been referring to the upcoming eLearning protocol as “Tin-Can API” due to the back and forth communication nature of this new standard. I think this name was well suited for the project initially, but it was starting to pose some problems. Specifically, in an industry where it can be hard to establish credibility, talking about “Tin-Can” didn’t do me any favors 🙂 . But, Tin-Can is no more. The API is now being labelled as “Experience API”. Initially thoughts? Not much better.
Personally, I am not one for cute or crafty names when it comes to this kind of thing. I can only imagine the conversations with clients…
“Yea, we need to make sure that we publish to Experience API”
“Are you publishing to SCORM v1.2, SCORM 2004, or Experience?”
“Does your current LMS publish to SCORM or Experience?”
“You should really considering upgrading to Experience API”
Ugh, I’m not looking forward to that. It just sound silly. Nonetheless, a rose by any other name is still a rose. This new direction for our industry is still the correct direction, regardless of the silly nomenclature.
If all this Tin-Can/Experience talk is new to you, then take a look at this post located on eLearning Industry.