Standard way to control initial value of @Version

Test rely on version value assertion is failed when switch from Hibernate to EclipseLink, because Hibernate starts from `0` but EclipseLink starts from `1`, It would be nice if the spec enforce it.
I'd like it starts from `1` because it's human readable then can be display in UI directly.

Start by reading the @Version specification and comparing the initial-value behavior described for Hibernate and EclipseLink. The work is done when the specification clearly defines a consistent initial version value and the provider behavior can be assessed against that requirement.

Written by the indexing model from the issue text.