bscSCORM

As written, we only allow for eventual consistency for statements, so we should be good to issue PUTs and then immediate GETs on documents in the conformance test and in...

@joshrussell a big 👍 to this from me. If I had it to do over again, the .../statements resource would always return a list, even if it was a list...

@garemoko @andyjohnson after we got off the call, I realized that this only really need apply to the alternate request version. I'm not it's worth making the distinction, but it...

@brianjmiller do you expect LRSs that want to support the alternate syntax will just continue to support 1.0, or rather just figure that the syntax is no longer needed?

I think it would be really bad to come up with three incompatible launch mechanisms. (ours, ADL, CMI-5). I think it would be worse for 1.0 to come out without...

@garemoko CMI-5 requires additional context which our launch mechanism isn't equipped to handle. I've been very involved in the launch discussions within the CMI-5 group, and expect that launch mechanism...

I've started a GitHub repository with our launch method: https://github.com/RusticiSoftware/launch/blob/master/lms_lrs.md For now, it's exactly what was in the linked document above, aside from re-formatting for markdown and fixing a couple...

re: @garemoko 's comment, we could provide an additional representation of the statement resource (rather than a replacement), in which case this wouldn't be a breaking change for clients. If...

@canweriotnow I should have been more clear, it's possible to encode using encodeURIComponent, but Apache's default behavior is to helpfully pre-decode any encoded `/` , so by the time an...

I also generally thing this falls on whatever is making the statements to avoid "duplicates" -- which I put in quotes because a big reason I'd be concerned about putting...