xAPI-Spec
xAPI-Spec copied to clipboard
adlnet
The xAPI Specification describes communication about learner activity and experiences between technologies.
In https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#stmtres "2.1.1 PUT Statements" under the "Details" it is said that the PUT endpoint "Stores a single Statement with the given id." However the last item in the "LRS...
I'm implementing an LMS + LRS that supports xAPI. In reading the spec there are a few things I'm finding unclear about "Documents" and "State". I'll post a separate issue...
Hi, As referenced in [my other ticket](https://github.com/adlnet/xAPI-Spec/issues/1102), I'm implementing some LRS capability and finding it strange that the spec invites end users (by way of JS in their browser) to...
Hey, new to xAPI this year and looking to understand what the logic is behind limiting to only allowing a single IFI per Actor (Agent). I ask because the use...
Dear xAPI-Spec software team provider, it seems that the server is down or limited. For example, when we click on the URL indicated in the sample or provided xAPI statements,...
Related issue: #475 Strings that are "fetched from the ui" and put into a statement may contain urls, and are allowed to in the current version of the spec. The...
I am concerned by the section on concurrency. > 3.1 Concurrency > ... > [Client Requirements](https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#client-requirements) > > The State Resource will permit PUT, POST and DELETE requests without concurrency...
We've recently come across an edge case where a system has used a [data URI](https://en.wikipedia.org/wiki/Data_URI_scheme) representing as an activity id. This appears to have occurred not by deliberate design, but...
Not rejecting extreme future timestamp statements to prevent issues due to clock errors is overkill
https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#247-timestamp > A Learning Record Provider MUST NOT use a future time for a "timestamp" property in a Statement. > An LRS SHOULD* NOT reject a timestamp for having a...
the xAPI specification should be updated to use SHA2 algorithms, as SHA1 is no longer recommended. For organizations capturing xAPI statements containing personally identifiable information (PII) of customers, using SHA1...
