Version # and versioning

[mlinksva]

The initial version should have some kind of identifier, and there should be some expectation set for how updates will be handled. Obvious options:

1. Version numbers, probably using loose translation of semantic versioning
2. Hash of document, any change gets new hash; requires precise rule about what is hashed
3. Date-based version, update gets new date-based version
4. Don't identify versions

I appreciate them all and they 1-3 mutually exclusive, but aren't often strung together. I don't know that there's a dominant practice. I suggest 1 for familiarity.

[mlinksva]

d0305af implements 1