rusticisoftware / launch Goto Github PK

In lms_lrs.md the example lunch link may be invalid, or at the very least overy complicated.

http://example.scorm.com/TCActivityProvider/   
?endpoint=http://example.scorm.com/lrs/   
&auth=OjFjMGY4NTYxNzUwOGI4YWY0NjFkNzU5MWUxMzE1ZGQ1   
&actor={ "name" : ["Project Tin Can"], "mbox" : ["mailto:[email protected]"] }   
&registration=760e3480-ba55-4991-94b0-01820dbd23a2   
&activity_id=http://example.scorm.com/tincan/example/simplestatement 

It appears that the actor query string paramater is JSON, but it's not a valid xAPI actor as the values for name and mbox are arrays of strings instead of plain strings. Is this intentional or a mistake? IMO, it would make the most sense for those to be strings as then the actor could be used without a transform in the derived xAPI statements.

I look forward to your clarifiaction. Thank you.

It leads to a 404.

Hi All,

Understood the concept of content_token and content endpoint, any code level example can be provided about how to generate "content_token and content endpoint"?

Thanks a lot
Alex

In addition to the launch link parameters described in the launch section, the following parameters will be provided as needed:

content_token: The authorization token to be included on requests to the content endpoint. If missing, the content is not protected and must be accessed directly.

content_endpoint: the absolute URL to use to access protected content. If content token is specified, but the endpoint is not, the TCAPI endpoint, with the postfix “content/” is to be used as the content endpoint.

When a client application needs to access a protected resource, it will first determine the path to the protected resource based on the content endpoint, and the relative path of the protected resource within the Tin Can package.

"Note that this methodology works for retrieving 1 resource at a time, an HTML document loaded in this way which includes relative paths would have broken links."

https://github.com/RusticiSoftware/launch/blob/master/lms_lrs.md#private-content-access-and-tin-can

Using relative paths is a best practice in self-contained websites to prevent breaking changes during deployment or distribution. This model could prevent some HTML content from working properly.