What's the use case for this?

How about a view object with id and parameters properties?

fugu13 <notifications@github.com> wrote:

>In xAPI.md:
>
>> @@ -1903,19 +1912,30 @@ Returns: 200 OK, [Statement Result](#retstmts) (See section 4.2 for details) > 			those parameters should also be specified. > 		</td> > 	</tr> > -	<tr><td>context</td><td>Boolean</td><td>True</td> > -		<td>When filtering on activities (object), include statements for which > -			any of the context activities match the specified object. > +	<tr><td>viewId</td><td>String</td><td> </td> 
>
>I see only a small reason to include an underspecified parameter like this. Easier to leave it off and allow view experimentation, especially as many of those views may be parameterizable themselves, thus needing even more parameters (and making it even less useful as an underspecified parameter, since there really won't be enough specification for tools to work with them).
>
>—
>Reply to this email directly or view it on GitHub.￼
>