auth parameter should include "Basic "

[garemoko]

Maybe this ship has sailed, but this is how this non-spec has been implemented in practice and the example here (well, the version copied on Articulate's website) confused at least 1 person.

[brianjmiller]

Whether or not you are correct (you probably are) I'm 👎 to any change in this document because it implies that it is actually maintained or maintainable. IMO it isn't and the sooner we get people to realize that it is deprecated and move to something like cmi5 the better off we'll all be. Having the last commit be over 2 years ago (and 4 years ago prior to that) is hopefully a signal that people should move on.

Having said that, if we can muster the strength what we should do is replace the readme content and the tag line of the repo to be explicit about deprecation and suggest to look at cmi5.

[garemoko]

I don't disagree with that.

Perhaps a better approach is for me to reach out to Articulate and get them to update their documentation (the relevant bit of which is pretty much copy-pasted from here). Since that's documenting what Storyline does, and doesn't give any indication that other authoring tools should follow like an update to this doc might. I might also suggest that they remove their link to the google docs that link here.

[ht2]

Hey @brianjmiller, do you have any examples of authoring tools that are compatible with the cmi5 Quartz version of content launching?

[brianjmiller]

@ht2 at the moment I don't. Our Driver product does, and so in theory any tool that uses it under the hood can with a fairly straightforward upgrade. Any tincan.xml package from Captivate can be upgraded in a straightforward fashion given a licensed copy of Driver. I'm also aware of Obsidian E-learning at least in the content testing phase and know of a couple others that are working on upgrades that will include the feature. Unfortunately we are in early stages with it, and it is a bit of a chicken and egg scenario between LMS/content support, but hopefully bringing it online in our Cloud product will provide the test bed needed for content developers and the rapid authoring tools they use to start working with it.

Having said all of that, because of the slow uptake of new standards I still think it is valuable to put them on notice by indicating that they need to be thinking about the next stage of the evolution of content backed by xAPI.

[brianjmiller]

@garemoko I think getting them to update the doc with their implementation would be a good way to go. I actually like having the link back to this as the canonical source, because then anyone clicking through sees the deprecation bit whenever it lands (even if we aren't ready for it yet).

The fact that this issue has been raised is important for the same reason, anyone coming to the repo or asking the same question in the future we are able to point to this as an admission as to why it is the way it is and why it wasn't changed which can be valuable.