Forum Discussion
URN vs URL in Storyline and Rise xAPI
Hi All:
Wondering if anyone can share why Rise uses a URL model in the xAPI export, but Storyline uses a URN. Any way to convert the URN to URL? Any reason for the difference?
Stuart
Hi Stuart,
Thanks for reaching out!
Rise 360 and Storyline 360 are two completely different applications which would explain why their output structures are different too. Is there a reason why you need Storyline 360 to follow Rise 360's identifier format? Are you having issues uploading your published Storyline 360 content to your LMS?
There isn't a way to convert the identifiers from one format to another, but I opened a support case on your behalf so our support engineers can share why their formats differ. Please keep and eye out from an email from them in your inbox!
Hi together,
usually, we have been using "http:// or https:// " instead of "urn:articulate:storyline:" through 360 as this follows the guidelines defined by https://xapi.com. It seems, that when we use the same "urn" for different languages it causes some issues with our LMS. We have no issues when using "http://". Do you have an update on this matter or why it was decided to use "urn" instead?
Mustafa
Hi MustafaAkpolad!
Sorry to hear that modifying the output structure in Storyline is causing issues within your LMS!
I would like our support engineers to have a closer look at the behavior you described, so I've opened a support case on your behalf. You're in great hands with them, and they should be following up with you shortly!
