// Agents, Personas and People So far in this Deep Dive series into the Document API we’ve looked at the State API and Activity Profile API. The Agent Profile API is similar to the Activity Profile API, but instead of Documents relating to Activities, it’s…
Read more
For storing (and sharing) state! Last time we dived into the Document APIs as a whole. This time we dive deeper into the most well known and commonly used of the Document APIs, the State API. As there’s a lot of similarity between the State…
Read more
What are the Document APIs and why should you care? xAPI’s Statements get a lot of attention and rightly so. Statements are the primary way of tracking the learner and set out a standard data structure for reporting tools to read. But Statements are not…
Read more
Was it the butler, or Mrs Brown with the Candlestick in the Conservatory? Choosing the actor of your xAPI statement can be a bit of a puzzle… Brian Miller’s deep dive into Agents is a great introduction into the technical structure of the Agent object…
Read more
As many of you know, we xAPI interns have been hard at work since we arrived in May. A couple of weeks ago, we released our first contribution, TinCanPython. It should look very familiar to anyone who has experience with the existing xAPI libraries (TinCanPHP,…
Read more
// Last week we introduced the concept of a Recipe, a defined way to capture the same experience using the same set of statements across Activity Providers. This post will delve a bit further into how we got to the concept and the technical…
Read more
As network speeds and the processing power of devices improves, the size of the files we use to capture our experiences, be they photos or other graphics, videos, or complex documents, increases. We need a way to associate these ever-growing files with the metadata capturing…
Read more
A little over a month ago I presented the "Anatomy of a xAPI Statement" webinar as follow up to our continuing Deep Dive series of blog posts. Despite some Q&A time at the end, I didn't have a chance to answer all the questions, here…
Read more
Several times throughout the Deep Dive series I’ve mentioned “catch all” objects and a future post — here it is. The framers of the Experience API specification knew that the overall structure of a statement, particularly with its oft mentioned Actor-Verb-Object pattern, could capture a…
Read more
Deep Dive: Result So far throughout the Deep Dive series that I’ve been writing, there has been one thing notably lacking, e-learning. It turns out that the framers of the Experience API specification hit on something big enough that it need not be boxed in…
Read more