Potentially Allowing the xAPI Version Header to Use 2.0.X

[vbhayden]

Afternoon gang!

It's been raised a few times in other areas, so I wanted to just poll the peanut gallery on it here.

As it stands, the only thing preventing an LRS from being compliant against both 1.0.3 and 2.0 (the newer IEEE variant) is the 1.0.3 requirement for an LRS to reject future headers.

The LRS MUST reject requests with a version header of 1.1.0 or greater.

I am personally in favor of loosening this requirement to allow instead for known xAPI versions that correspond to an IEEE version, but also don't want to randomly change a spec document without community approval.

If you have any opinions on this, feel free to share them here. I'm sure some folks would appreciate being able to consider their LRS products as compliant to both specs, which the Adopter Registry now supports btw.

[bscSCORM]

Maybe this just needs an "unless such requests are routed..." like the similar:

The LRS MUST reject requests with version header prior to version 1.0.0 unless such requests are routed to a fully conformant implementation of the prior version specified in the header.

From a test point of view, that probably means sending versions like 1.1.0 and 3.0 to validate this, because in practice it's going to hard to validate that "unless"

It seems undesirable for an LRS that doesn't actually conform to 2.0 to accept 2.0 requests