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've been reflecting on this and I think there's limited advantages of either approach on the basis that:

* In theory, patch releases don't change behaviour, they only clarify so there is no difference at all between a 1.0.0 statement and a 1.0.3 statement. 
* This means there's no advantage to using a particular patch version (other than the document being clearer). An adopter could follow the 1.0.3 document and claim to be adopting 1.0.0; 1.0.3 only clarifies what 1.0.0 meant but didn't say clearly. The MUST here doesn't really have any teeth. 
* This also means that the patch number in the version property is theoretically meaningless. 

The disadvantage of upping the patch number then is it implies some difference which isn't there. There's also the point that there's some work to do to bump that number up, although in practice that's not really an issue because the implementer could claim to be using the earlier patch and not update the number if it's a big deal. 

The advantage is that in practice we may have changed something we shouldn't and knowing the patch number may be useful in future for some reason. It also seems to be the intend of 1.0.0 which specifically allows for patch numbers other than 0 (see the first LRS requirement in this section). 

I agree with Brian on making this generic, though we need to be careful how we word it to avoid saying that "everybody must use 1.0.3 immediately". I agree for two reasons: Firstly maintainability and secondly, this also applies to 1.0.1 and 1.0.2.