I thought it might be. In that case please merge.

fugu13 <notifications@github.com> wrote:

>In xAPI.md:
>
>> @@ -958,15 +958,20 @@ Interaction components are defined as follows: > 	<tr> > 		<td>id</td> > 		<td>String</td> > -		<td>As in "cmi.interactions.n.id" as defined in the SCORM 2004 4th > -			Edition Run-Time Environment</td> > +		<td>A value such as used in practice for "cmi.interactions.n.id" as 
>
>Yep, it's supposed to be vague. The problem is the actual 2004 4th edition RTE requires it to be a URI, but no one ever did that, so there're tons of non-URI values we need to support -- but any LRS that did that would have violated the data type conformance requirements. The uniqueness req later down gives it the main property it needs for usefulness.
>
>Sent from my iPad On Apr 25, 2013, at 4:33 AM, Andrew Downes <notifications@github.com> wrote: In xAPI.md:
>
>@@ -958,15 +958,20 @@ Interaction components are defined as follows: 	<tr> 		<td>id</td> 		<td>String</td> -		<td>As in "cmi.interactions.n.id" as defined in the SCORM 2004 4th -			Edition Run-Time Environment</td> +		<td>A value such as used in practice for "cmi.interactions.n.id" as
>
>This is vague. I'm not sure if that's deliberate or not :-) I'm happy to merge as it is, but if it's not supposed to be vague then it should be clearer. — Reply to this email directly or view it on GitHub<https://github.com/adlnet/xAPI-Spec/pull/279/files#r3955609> .
>
>—
>Reply to this email directly or view it on GitHub.￼
>