Is Tin Can the same as xAPI?
Tin Can, Experience API, xAPI – three names for the same thing. The short version is that it’s all the same thing, we call it Experience API or xAPI, but you can call it whichever you like!
Why is xAPI called tin can?
could be adapted to suit the next generation of eLearning. xAPI is the result of that work. Rustici chose the name project name “Tin Can” to describe the two-way conversations the technology would track as it made it easier for learning systems to communicate with each other.
What is xAPI content?
Experience API (also xAPI or Tin Can API) is a learning technology interoperability specification that makes it easier for learning technology products to communicate and work with one another.
What is xAPI format?
The Experience API (or xAPI) is a new specification for learning technology that makes it possible to collect data about the wide range of experiences a person has (online and offline). This API captures data in a consistent format about a person or group’s activities from many technologies.
What is xAPI statements?
Verbs in xAPI are URIs, and should be paired with a short display string. They are a crucial element of statements, as they describe just what has happened between the actor and object of the statement. The xAPI specification (1.0.0 at the time of this writing) allows any full URI to be used as a verb.
What is xAPI tracking?
xAPI makes it possible to record learning from many sources in a single record-keeping system. xAPI allows learning content to be distributed across multiple sources. xAPI can capture learning experiences from mobile applications, social learning, eBooks, and from games.
What can xAPI do?
xAPI is a simple, lightweight way to store and retrieve records about learners and share these data across platforms. These records (known as activity statements) can be captured in a consistent format from any number of sources (known as activity providers) and they are aggregated in a learning record store (LRS).
What is xAPI and LRS?
Learning Record Store (LRS) = A place to store learning records. The LRS is the heart of any Experience API (xAPI) ecosystem; receiving, storing and returning data about learning experiences, achievements and job performance. You’ll need an LRS in order to do anything with xAPI.
Who owns xAPI?
Rustici Software
Rustici Software is the company behind xAPI.com. We manage and maintain the resources on this website to help people learn about and get started with the standard.
What can xAPI track?
xAPI can capture learning experiences from mobile applications, social learning, eBooks, and from games.
Is xAPI a REST API?
The data format xAPI uses is JavaScript Object Notation (JSON). To align with current web best practices, a RESTful approach is used with all xAPI requests.
What is LXP platform?
A learning experience platform (LXP) is an AI-driven peer learning experience platform delivered using software as a service (SaaS). LXPs were born out of a new approach to corporate learning platforms, addressing perceived shortcomings with learning management systems (LMS).
What is the difference between Tin can and Experience API?
There’s no difference at all between Tin Can and Experience API; zero, nothing, nada. People sometimes think that they’re two separate forks of the project, one owned by Rustici Software and one owned by ADL, but that’s absolutely not the case.
What is the xAPI API?
This API captures data in a consistent format about a person or group’s activities from many technologies. Very different systems are able to securely communicate by capturing and sharing this stream of activities using xAPI’s simple vocabulary.
What is an external tin can activity?
External Tin Can activities include but are not limited to mobile apps, offline learning, web application, collaborative learning, games, videos, etc. When an external activity needs to be recorded, the application sends secure statements to the LRS to record all statements.
Why is it called Project Tin Can?
We called this process Project Tin Can because it was meant to be a two-way conversation between us and the eLearning industry. We not only realized the standard, we wrote it. Now that it’s in the community’s hands and actively developed by many developers and businesses, we are more engaged than ever.