Greetings all,
First time poster here as well. Had to chime in as I just couldnt figure out what I was doing wrong last week in sending my satements.
I know this might sound completely obserd, but I was missing my result. As I initially understood, I thought I only needed to send the Actor, Verb, Object.... not quite.
The key I was missing was the result... yeah, Ooops. The object needed a result.
The best example that got me over my hump was Will Chinda's.
Great stuff, also using Tin Cans statement viewer and golf examples really helped me understand how the statements were being sent/received.
As you all can tell, I'm the new guy at xAPI, but quickly finding out its much different it is than SCORM. I'm sure others can explain at much greater details, but scince I'm the FNG at all this, here is whats rolling in my head.
1st -SCORM requires a PIF file be loaded on an LMS.
2nd- SCORM requires a strict/loose imsmanifest with all sequencing and resources defined in the PIF.
3rd-SCORM requires the initiate and terminate (...or, suspend) calls be sent for each session.
xAPI only needs to know where your LRS is, the authentication to post the statements and what the activity did ...including the result...of the Actor, Verb, Object. Each one of these can get deep as I'm finding, but it is just based on the three needs.
We are targeting a sunset of our LMS and only use our home cooked LRS. This breaks the cost molds of LMS dependencies HW/SW (including SCORM cloud). This also allows us to focus in on the learning activities first, rather than the tech rules and boundaries.
We essentially, are aiming to manage and host our own content where ever, however we want (adhering to best practices and standards). We only need the content to send the statements to our LRS.
It does sound like a great group and looking forward to the discussions.
Thank you for your support,
-Roger
Sent from my T-Mobile 4G LTE Device