This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Facts: Next week, the IEEELTSCxAPI TAG will be taking a vote about if and which aspects of xAPI 1.0.3 to propose to the broader IEEE for consideration as a standard. More important: the nexus of xAPI work is moving toward this group, and it’s active. The work matters, and it needs a home. The Details.
Shelly Blake-Plock announced last night via LinkedIn that he would be leading a Technical Advisory Group (TAG) for IEEELTSC (Learning Technologies Standards Committee). Our start point is the xAPI 1.0.3 We’ll discuss all aspects of xAPI such as xAPI Profiles and the relation of xAPI to SCORM and cmi5.
xAPI turned 10 years old in April, the oldest versions of SCORM are over 21, and even the “new kid” cmi5 is now 7. The IEEE board approved “ IEEE 9274.1.1-2023 2023 ” aka – and much easier to remember – xAPI 2.0. So does this mean you have to do anything right now if you’re leveraging xAPI in your platform?
To be honest, I am struggling to discern which pieces of work would best support the xAPI community and Rustici Software. There’s good work happening at the IEEELTSC TAG xAPI , and we’re doing a bit of it. We’re talking about it here frequently, and haven’t reached consensus. We’re active, yes.
xAPI and LRS (Learning Record Stores) have been in the news and frankly everywhere within the e-learning industry in the past 1.5 on a side note – I – me, was always told that xAPI and Tin Can are one in the same). ADL, IEEE and many people and businesses talking about this technology call it xAPI.
We were shocked to see how many people joined Chris Tompkins and Brian Miller on “Our IEEELTSC voting members recap 2023 and what’s next for the standards” webinar last week. What happened in 2023 xAPI 2.0 becomes a standard In late March, the IEEE approved “ IEEE 9274.1.1-2023 2023 ” – or xAPI 2.0.
We organize all of the trending information in your field so you don't have to. Join 59,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content