fugu13

Looks like those were added together intentionally in https://github.com/adlnet/xAPI-Spec/commit/0c861ecbb8259ff2cccd30d2281ce4547ab665b2 Definitely an area we could touch up in a future version.

Even with the star it's only a SHOULD NOT, so we shouldn't change it until a substantial version ticks (keeping this issue around and labeling with next version should be...

API is commonly used to describe specifications for their implementations, which are also called APIs. The term's more than a bit overloaded ;)

Thanks for the input! Right now the preferred way to indicate and filter on topics statements are related to is to use contextActivities (in context), probably with the (new in...

You can already get that effect with the data URI approach Example context: ``` javascript { "contextActivities": { "category": [ {"id": "data:itmightbebunnies"}, {"id": "data:hoppylegs"}, {"id": "data:twitchylittlenoses"}, {"id": "data:whatswithallthecarrots"} ] }...

We're using Oathkeeper more and more where I work (ModusBox), and getting ready to expand that use considerably as part of a centralized IAM setup for hosted customer APIs, and...

I could work up a proposal like that. Very loosely, where I'd be inclined to start would be a new mutator under the existing approach that works similar to the...

@FlorianTolk no, those being subclasses of statement is nonsense, and this was pointed out quite a while ago and still isn’t fixed

Statement should never derive from object. You could model sub statement, agent, and activity as deriving from some highly abstract “object”, but that’s honestly a very awkward way to model...

This is far from the only change that should be done to the ontologies. When I reviewed them a while back they were so flawed as to be unusable (the...