xAPI-Spec
xAPI-Spec copied to clipboard
adlnet
The xAPI Specification describes communication about learner activity and experiences between technologies.
>The LRS SHOULD* reject any request with 400 Bad Request status where the content type header does not match the content included in the request or where the structure of...
The word "Activity Object" in the requirement "Every value in the contextActivities Object MUST be either a single Activity Object or an array of Activity Objects." could link to: `#2441-when-the-objecttype-is-activity`
While there aren't core verbs in the xAPI Spec, there were a collection of "SCORMlike" verbs established early in xAPI that have seen wide use in practice. These verbs have...
Hi, I have a question in regards to statement aggregation and [alternative request syntax](https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#alt-request-syntax) >All xAPI requests issued MUST be POST. This requirement includes `more` IRLs from StatementResult responses? Example:...
Need to update the spec to be consistent. We currently use e.g. in some cases and e.g., in others...this seems to be a British vs. American English preference. I don't...
Hey all, just looking for clarification with the expected behaviour of the LRS when receiving a PUT request without ETag headers (If-Match and If-None-Match). The [client requirements](https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#client-requirements) seem to suggest...
"JSONLD @context for TinCanSchema (Experience API: xAPI)" https://github.com/RusticiSoftware/TinCanSchema/issues/6 > - https://en.wikipedia.org/wiki/JSON-LD > - https://www.npmjs.com/package/schema-jsonld-context - ``@context`` - https://www.w3.org/TR/json-ld/#the-context - https://www.w3.org/TR/json-ld/#advanced-context-usage - https://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld - ``"@container": "@list"`` https://www.w3.org/TR/json-ld/#sets-and-lists ([``rdf:List``](https://www.w3.org/TR/rdf-schema/#ch_list), ``rdf:first``, ``rdf:rest``)` -...
After talking about merging a recent PR around fixing a mistake in an example in the specification, @garemoko raised a good point - should we allow master to be modified...
In xAPI we already have a concept of personas associated together as people. I've seen a few cases recently where an organization is looking at migrating to a new platform...
Can an LRS return an earlier Consistent Through time than it has returned to in a previous request?
Especially in the context of attachments, where statements-con-attachments are available later than statements-sans-attachments. See https://github.com/adlnet/lrs-conformance-test-suite/issues/207#issuecomment-314103768 and discussion there.