I put this in before I worked out how to do asynchronous calls. My view now is that if you want multiple agents you should do multiple requests.

bscSCORM <notifications@github.com> wrote:

>In xAPI.md:
>
>> @@ -1877,6 +1879,15 @@ Returns: 200 OK, [Statement Result](#retstmts) (See section 4.2 for details) > 		<td>Maximum number of statements to return. 0 indicates return the > 			maximum the server will allow.</td> > 	</tr> > +	<tr><td>sizeLimit</td><td>Nonnegative Integer</td><td>0</td> > +		<td>Maximum size of statements to return in bytes. 0 indicates return the > +			maximum the server will allow.</td> > +	</tr> > +	<tr><td>authority</td><td>Array of Agents</td><td>0</td> > +		<td>Only statements with the authority of one of the listed agents are returned. > +		Where the authority is a group, the LRS will return statements where any member > +		of the group is matched.</td> > +	</tr> 
>
>@fugu13 @garemoko I had been thinking:
>
>only 'identified' groups should be allowed as query parameters'identified' groups may not have members, so matching on members is irrelevantif an actor or identified group passed as a parameter matches exactly, or is a member of an ad-hoc group in the target field in the statement, then the filter condition matches
>
>I suppose the ad hoc groups approach above would be a way to query on multiple actors at once, which might be nice, but it seems odd to have an ad hoc group of [Andrew, Russel, Ben] match a statement that just talks about "Russel".
>
>—
>Reply to this email directly or view it on GitHub.￼
>