That work work, but it might be simpler just to add:

If the statement has been voided or uses verbs, activity types or properties not included in the 0.9 specification, do not convert it.

Andrew

bscSCORM <notifications@github.com> wrote:

>In xAPI.md:
>
>> + > +####Rationale: > +This is a 1.0 specification, and as such implementers should not have to consider prior > +versions of the specification. However, prior versions did see notable adoption. This data > +conversion is specified in order > +to preserve the data tracked using earlier versions, and make it available to new implementers > +in a consistant manner. > + > +####Details: > + > +#####Conversion of statements created based on version 0.9 > + > +A 1.0 system converting a statement created in 0.9 MUST follow the steps below: > + > +* If the statement is voided, do not convert it. > +* Prefix "verb" with "http://adlnet.gov/expapi/verbs/". 
>
>These are short lists that are not subject to edit (the original 0.9 verbs), I'd rather just include those lists. Does that work for you? I think the scenario where someone added a verb in 0.9 that wasn't valid in 0.9 which happens to have been added to the ADL verb list isn't worth worrying about.
>
>—
>Reply to this email directly or view it on GitHub.￼
>