Today we’re excited to announce support for a new specification in SCORM Cloud- cmi5, which is something that doesn’t happen all that often in its history. Along with making cmi5 support readily available in SCORM Cloud, we’ve also added support for cmi5 to some of our other products including SCORM Engine and SCORM Driver.
Obviously, supporting a variety of specifications is a huge part of what we do well at Rustici Software. More than anything, though, I think it’s important for us to be conscious of, and to explain well to all of you, when and why we add support for a particular specification.
So, what is cmi5?
cmi5 is technically a profile of xAPI which means it piggy backs on top of things already well defined in xAPI, but adds specificity in others. For cmi5, this means that certain xAPI statements are required, and launch is handled in a very specific way.
For me, it’s the launch piece that’s so important. From xAPI’s advent years ago, there have been issues with launching content. In the earliest days, we at Rustici Software defined a very simple launch specification that several content vendors picked up on. It was good enough for the time being, but it wasn’t really good enough in practice.
So, over the last couple of years, many people including Bill McDonald (as Chair of the working group) and Art Werkenthin and others at RISC have put a lot of energy into considering how their AICC work could be applied to launch in the xAPI world. The result is that we have a good solution for launching content via xAPI.
Why it matters
Years ago, as we at Rustici Software and others around us started evangelizing xAPI, we made some mistakes. We talked about all of the things that could be enabled by xAPI, the things for which it was necessary but not sufficient. Over the last year or two, we’ve really started to fill in the gaps to make it sufficient as well. And while launch isn’t the dreamiest of capabilities for which xAPI is a solution, it is absolutely fundamental.
If content launch is ultimately going to transition from SCORM to xAPI, cmi5’s support for launch will be a requirement. And further, so many other activities actually benefit from having a well defined, implemented, and adopted specification for launch. So for now, we’re excited to share that Cloud now offers vendors and others a great place to test cmi5 based launchable activities. We hope this helps spur the development of many xAPI/cmi5 adopters.
When it comes to getting something for free, I’ll do just about anything. Last summer, we had a new ice cream store open in East Nashville. The night before they “officially” opened, they were offering free ice cream. I stood in line for close to 2 hours in 90 plus degree weather in June for two scoops of ice cream. It was by far the most delectable ice cream I had ever eaten, but ice cream none the less. You may think that’s a bit extreme but I like to think of it as getting a good deal. Helps me sleep at night, anyways.
You pay for Rustici Software products, and we want to make sure that you’re getting the most out of them.
Some of our customers prefer to tuck their use of our products away, and we’re fine with that. But others want to scream from the mountaintop that they’re using the best SCORM conformance software available. If you’re a screamer, then we want you to let the world know that you’re using our stuff. We’ve waded through all the legalese and created a way for you to do just that.
“Powered by” images are now available for you to put to work. Just visit our “powered by” page and grab the HTML or files for print that you need.
We’ve provided 3 sizes for each image, but we understand that there will be exceptions. If you need a different size or format, just email firstname.lastname@example.org with your needs and we’ll get a custom image made for you — pronto.
There are so many channels now. Whether we’re talking radio, TV, or the web in general, there are so many ways that information is pouring over us.
Like many companies, we’re doing our best to reach everyone wherever they are… Of late, we’ve been finding that people are missing some important things we have to say. So, I wanted to lay out the different places we’re talking so you can be sure to visit if you care.
Well, you’re here, so you must know about it already. For the most part, we tell our big stories here. Big new projects and products, major software releases, occasional client announcements, and industry brouhahas.
Many of you probably have no idea that our support forum even exists. We’re constantly answering questions from customers and others in these forums. As a customer, you’re invited to create tickets whenever you have a question you’d really like help with.
More than anything, though, I’d really like to see our customers subscribing to the forum for the product they license. SCORM Engine customers can follow the RSS feed or use the built in email subscription. No matter how you do it, this is a great way to know about our newest releases. (This applies to SCORM Driver customers too, of course.)
Project Tin Can
Project Tin Can might be the most important bit of work we’re doing these days. Along with a huge community of real SCORM users, we’re helping to figure out what comes next for SCORM and learning experiences in general. You can see our contributions daily on the User Voice site, and we’d love to see your contributions there as well. You can also follow @projecttincan on twitter.
If you’re a big SCORM Cloud user, we also use twitter to let the world know when we’re having issues or changes. @scormcloud is pretty quiet, but it could be useful in an emergency. (SCORM Engine and SCORM Driver even have accounts, but we rarely use them.)
That’s the big picture. If you need something you’re always welcome to call or email too. My phone number is 615.550.9522 (yes, that’s me, directly) and my email address is email@example.com. I actually want to hear from you, so bring it on.