We discussed tense as part of substatements. Can't remember outcome but at this stage we should follow what that section says.

Andy Johnson <notifications@github.com> wrote:

>  a verb with this meaning has been defined with this id. This applies to all example verbs given in this
>  specification document, with the exception of the reserved verb <a href="#voided">'http://adlnet.gov/expapi/verbs/voided'</a>.
> +
> +##### 4.1.3.1 Use in Language and Semantics of Verbs
> +
> +###### Semantics
> +The URI represented by the Verb id identifies the particular semantics of a word, not the word itself.
> +
> +For example, the English word "fired" could mean different things depending on context, such as "fired a
> +weapon", "fired a kiln", or "fired an employee". In this case, a URI MUST identify one of these specific
> +meanings, not the word "fired".
> +
> +The display property has some flexibility, especially in regards to specificity or tense.  For example,
> +while Verbs are established in the past tense, certain systems may want to display certain
> +statements in other tenses.  Similarly, a series of statements relating to text, audio, and video all
> +may be tagged by an id corresponding to “experienced”, but the display property may use “read”, “listened to” and “watched”.

Do we have agreement on tense?  I do see the conflict in a "branching" type behavior and will raise it as a part of the issue of the rigidity of some of the verb requirements.

---
Reply to this email directly or view it on GitHub:
https://github.com/adlnet/xAPI-Spec/pull/230/files#r3904685