Just a thought: another possibility is to have the activity api queryable by activity type. A reporting tool could then get all the activity ids that have a type, and then query for those activity by activity.

Andrew

bscSCORM <notifications@github.com> wrote:

>In xAPI.md:
>
>> @@ -1844,6 +1846,9 @@ Returns: 200 OK, [Statement Result](#retstmts) (See section 4.2 for details) > 			against object property of statements. > 		</td> > 	</tr> > +	<tr><td>activityType</td><td>String</td><td> </td> > +		<td>Filter, only return statements matching the specified activity type id.</td> > +	</tr> 
>
>@fugu13 would be curious to get your thoughts on this.
>
>I see how it could be important to filter. Besides philosophical resistance to adding too much to the query API, and concerns that this will need a long interpretation discussion, I think this will be more difficult than it sounds for LRSs to implement (efficiently).
>
>My biggest concern by far would be any confusion/discussion about the behavior, and if anyone is going to champion the "just filter activity type as written in each statement" approach I think it would be Russel, so curious to hear what he has to say there before I worry too much about the other points.
>
>—
>Reply to this email directly or view it on GitHub.￼
>