Miscellaneous Version Changes

We are now in 1.0.3, so I've updated this in some places, will do a sweeping change for the rest upon confirmation

Felt that LRS MUST accept may leave some cases that an LRS MUST NOT reject was clearer about (picky, I know, but seemed more accurate)

We can't enforce a description will be meaningful, so I changed that part to a SHOULD

Header language wasn't disambiguating name from value, so I added the value to the corresponding tag

Finally, I don't think we care too much if systems convert between the 1.0.Xs, what we care about are breaking changes i.e. minor and major versions.
I'm okay with this as well, having the "latest" version up is a bit
dangerous.

As far as the converting Statements requirement, I don't like it in the
first place, but was just trying to hint that converting Statements between
minor and major versions with breaking changes is different than the patch
versions.

On Wed, Dec 10, 2014 at 8:49 AM, Jason Lewis <notifications@github.com>
wrote:

> In xAPI.md
> <https://github.com/adlnet/xAPI-Spec/pull/551#discussion-diff-21603577>:
>
> >  * An LRS MUST reject all Statements with a version specified that does not start with "1.0.".
> >  * Statements returned by an LRS MUST retain the version they are accepted with. If they
> > -lack a version, the version MUST be set to 1.0.0.
> > +lack a version, the version MUST be set to 1.0.3.
>
> @brianjmiller <https://github.com/brianjmiller>
>
> Is it time to switch to a branching model for the spec so that we can work
> on it in interim states then only merge at a release point and tag?
>
> In short:
>
> [image: yes]
> <https://camo.githubusercontent.com/a40a4efc6800888e723d444e4bb79b8ac80f07ed/687474703a2f2f692e67697068792e636f6d2f36395447567a7932496b6d66432e676966>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/adlnet/xAPI-Spec/pull/551/files#r21603577>.
>



-- 
Andy Johnson
ADL Technical Team
608-318-0049