- Get Started
- Write Code
Posted by Tim Martin
Posted 20 July 2017
Just a little editor’s note for everyone. You may notice that this site now redirects you more aggressively toward its experienceapi.com representation. In 2015, we heavily revised experienceapi.com and established that, when it came to using xAPI vs. Tin Can, “We call it whatever you call it.” Our goal was to provide resources and advice to people in the way they were looking for it. If they wanted to use “Experience API,” that’s what we’d use. If they wanted to use “Tin Can,” we were on board.
Both in real life and here on the website, we’re pushing a little harder toward xAPI at this point. We’re never going to yell at someone who says Tin Can, but we may just refer to it as xAPI. You’ll also see that we’ve changed all of the references to be explicitly xAPI rather than Tin Can. I promise, we’ve done something more than just “find and replace”, but if you happen upon a place where we missed a Tin Can reference, feel free to let us know. The one caveat is that we’re keeping historical references to “Project Tin Can,” the origin of the Experience API.
We’ll also be updating our prototypes to the new language. As anyone who writes code can appreciate, changing code doesn’t happen overnight, so it will take some time.
Posted by Tim Martin
Posted 14 February 2017
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.
Posted by Tim Martin
Posted 2 February 2016
Welcome to week one of the post-acquisition Rustici Software world. I just thought I’d take a moment here to discuss one of the reasons we agreed to sell Rustici Software to LTG, because it’s not all about the money.
Mike and I were seeking investment funding for Watershed, but we really weren’t on the lookout for anything related to Rustici Software. It was a profitable business, I know very well how to run it, and we have several sets of work that give us cause for optimism. LTG, however, saw the value in both Watershed from an investment point of view and Rustici Software from a market and profitability point of view.
After LTG’s first visit, Mike and I asked ourselves two questions.
Throughout the negotiations, due diligence, and these two long days as an LTG company 😉 we’ve consistently believed that we could do both of those things and still do. LTG is not an LMS provider like some of our prior suitors have been. We always used to worry that an acquisition of that sort might include aggressive interactions with our customers. With LTG, we’re going to continue to be agnostic, supportive of the standards, and generally the same company we always have been. We’re excited about it, and excited about continuing to support our customers and the industry in general in exactly the same way.
Posted by Tim Martin
Posted 29 January 2016
Today, I want to share a piece of news that’s really exciting for us. As of this morning, Rustici Software has been acquired by Learning Technologies Group plc (LTG), a publicly listed learning technologies agency made up of specialist digital learning businesses. As a part of LTG, we’ll have the opportunity to work with the other Group companies in creating the next generation of technically-focused learning solutions.
LTG has a great deal of learning expertise and serves organizations worldwide. LTG’s portfolio includes LEO, a pioneering learning technologies firm, the multi-device authoring tool gomo learning, games with purpose company Preloaded, and Eukleia, an e-learning provider to the financial services sector.
As part of LTG, we’ll continue offering exactly the same services we do today to an ever larger group — not only will we provide our world-class e-learning standards support to LTG companies and their customers but as part of the Group, we’ll also have the platform to reach new global audiences.
This has no impact on the xAPI/Tin Can API. We’ll still continue to work with ADL and the e-learning community to foster adoption and advancement of the specification.
For our Rustici Software customers, the story is simple. The very same people will be providing to you the very same services in the same way. Our ability to serve our customers in the way we always have is something we feel really strongly about.
We’re excited to have the opportunity to work with the fine folks at LTG, and to continue to serve the e-learning industry in an even bigger way than before. We’re also excited because we’re spinning off Watershed at the very same time. Watershed will continue to push forward with their exploration of learning analytics and LRSs, and has also received a significant investment from LTG as part of Watershed’s Series A funding round. Mike and I, as CEO of Watershed and CEO of Rustici Software respectively, are both excited about where the two companies are headed.
If you have any questions or need more specific information regarding the acquisition, please let us know. Any inquiries or requests for additional documentation should be sent to firstname.lastname@example.org.
Posted by Tim Martin
Posted 20 August 2015
On August 13th, 2015, we launched a heavily revised version of tincanapi.com. Andrew Downes has been working away, as he does, creating new content. Rather than direct it all at the blog, though, he’s been rethinking and restructuring the core site and sharing his insights for first-timers, learning designers, learning product vendors, and organizations. There are countless other updates laid out below. Please spend some time with them.
Many readers of the site, though, will likely notice a significant change to our handling of the name… tincanapi.com. Years ago, Mike shared our perspective on the name, that we were going to call it Tin Can API. For some, this has been a contentious issue. With the new site, we’ve made the site behave as we have been personally for a long time. We call it whatever you call it.
On the site, you’ll notice a toggle in the upper left. If you prefer to call it Tin Can, do so. If you prefer xAPI, that’s great too. Whether you visit tincanapi.com or experienceapi.com, the site will present everything to you using your preferred name.
It comes down to this: arguing about an API’s name simply isn’t productive. We have far more important things to accomplish together.
So please, enjoy the new content. Go build a brilliant activity provider. Make some statements. Or ask us for help if you need it.
Here are the new sections of the site:
The existing Tin Can Explained page gives a really helpful introduction to Tin Can if you’ve never heard of it. We’ve brought this section up to date a little and added some pages around the different components of the new enterprise learning ecosystem that Tin Can enables. We’ve also added pages targeted specifically at organizations, learning product vendors and vendors of products outside L&D.
By now, if you haven’t heard of Tin Can and got a basic understanding, you’ve probably been living on mars. These days, the question we get asked most isn’t “what’s Tin Can?” but “how do I get started?” If that’s your question, then good news – we’ve created a new section just for you!
The get started section includes pages targeted at product vendors, content authors and organizations. It includes guides to help you see Tin Can in action, get a Learning Record Store (LRS) and run a pilot project in your organization. There’s a collection of pages to help you think about moving on from SCORM, too.
We already had a bunch of resources for developers, but not much really aimed at learning designers. We’ve added a page outlining the impact of Tin Can on learning design, including reflections on a handful of learning models and theories in the light of Tin Can. If you’re thinking more at the strategy level, we’ve got a page on incorporating Tin Can into your learning strategy, too.
The developers section was already crammed full of resources. We’ve tidied these up to make them easier to find and created an interactive statement explorer page to help you understand the structure of the statement.
The statement generator we created a few years ago was due for an update and ADL recently published a new more comprehensive statement generator. We don’t believe in reinventing the wheel, so we’ve taken the ADL tool, made it orange and included it on the site.
To help you put all these resources into practice, we’ve created a series of challenges for developers to try out writing code for Tin Can.
The previous webinar list contained embedded YouTube videos for all our webinars. We’ve got so many webinar recordings now that it was getting hard to find webinars on specific topics so we’ve created a new categorized webinar list. Each of the webinars is now on its own page, making it easier to share the recording with other people.