xAPI-Spec
xAPI-Spec copied to clipboard
adlnet
The xAPI Specification describes communication about learner activity and experiences between technologies.
It never actually says if ascending is false returned data must be sorted in descending order, though that is the requirement.
This would be a 1.1.0 thing or possibly something for a separate reporting spec. It'd be really nice to be able to request statements and not have the LRS return...
As I've been digging more and more into the xAPI specification, it's become pretty clear to me that I have no clue how some of these APIs are supposed to...
Related: #829, #836. Adding a separate issue to add Travis CI to run `mdl` on PRs pre-merge to ensure consistent and proper formatting... I'll set up another PR for the...
When working on #828 (and its predecessors) I had some issues with whitespace... I noticed 2 things that might be worth reviewing just for ease of continued maintenance: - [...
From PR #945, but tabled until 1.1: > As of May 2015, JSON Web Signatures have left "draft" status and been officially endorsed as RFC 7515. This PR updates the...
This is a bit strong; anonymous data can be useful. Just needs re-wording a little. See http://tincanapi.com/2013/06/05/deep-dive-actor-agent/#comment-1836520796
Right now, "Requirements for Attachment Statement Batches" requires this of requests: > MUST include a Content-Transfer-Encoding parameter with a value of "binary" in each part's header after the first (statements)...
I'd like to use a cookie-based authentication scheme with my LRS, and this will require a slight change in its behavior. Specifically, the response to an incoming CORS preflight or...
I get the point of not allowing LRSs to reject statements based on non-recognized extensions, but it seems to me that this is akin to saying "take this stuff that...