Hello... it was brought to my attention an XML file generated when publishing contains multiple uses of a URL apparently tied to xAPI... http://adlnet.gov/expapi/activities/module
Can anyone tell me what this is? I have to assume it is automatically used because my course does not reference this URL.
Hi again Thomas! :) So I really had to put my reading glasses on for this one. I didn't even know I needed reading glasses.
That language in your published output is automatically put there by Storyline. When you publish for Tin Can API, the format has to follow a standard according to the Tin Can API protocol. This document explains in detail on page 14: http://scorm.com/wp-content/assets/tincandocs/TinCanAPI.pdf
A system reading a statement MUST NOT use the display property to infer any meaning from the statement, rather it MUST use the verb URI to infer meaning, and the display property only for display to a human.
So, when we say http://adlnet.gov/expapi/activities/module, the LMS is supposed to go to that URL and figure out the definition of module. It's a standard that Articulate cannot change or eliminate, and you can't remove those URLs from your published output.
So, I know from your other discussion that you might have a problem with references to external URLs. I would start with that explanation ^ and see where it takes you.
3 Replies
Hi again Thomas! :) So I really had to put my reading glasses on for this one. I didn't even know I needed reading glasses.
That language in your published output is automatically put there by Storyline. When you publish for Tin Can API, the format has to follow a standard according to the Tin Can API protocol. This document explains in detail on page 14:
http://scorm.com/wp-content/assets/tincandocs/TinCanAPI.pdf
A system reading a statement MUST NOT use the display property to infer any meaning from the statement, rather it MUST use the verb URI to infer meaning, and the display property only for display to a human.
So, when we say http://adlnet.gov/expapi/activities/module, the LMS is supposed to go to that URL and figure out the definition of module. It's a standard that Articulate cannot change or eliminate, and you can't remove those URLs from your published output.
So, I know from your other discussion that you might have a problem with references to external URLs. I would start with that explanation ^ and see where it takes you.
Thanks so much for your reply, Crystal. I'm beginning to understand. :-)
I'm right there with you! Fortunately I have a good team behind me. *I updated my post to read page 14, not 9. Sorry!
This discussion is closed. You can start a new discussion or contact Articulate Support.