Specification versioning and change log

[dennisvang]

From the readme it is not immediately clear to me which strategy is used for specification versioning.

The version format 1.0.0 of the current release suggests some form of Semantic Versioning, as in MAJOR.MINOR.PATCH.
Is that correct?

If not, what are the implications of major/minor/patch version number changes, with regard to spec compliance?

Closely related to the above, I think a consistent change log would be very helpful.
See e.g. W3C Process Document 6.2.3. Classes of Changes and keepachangelog.com.

Some related links and examples:

• W3 TR version management
• Semantic Versioning
• SCAP 1.3 Component Specification Version Updates

[konradana]

Yes, the idea is to follow Semantic Versioning. Currently, there has only been one release (1.0.0), so there is no change log. For the next versions, there should be one.

[dennisvang]

@konradana Thank you for clarifying.

Actually, I do still wonder about the implications of major/minor/patch version number changes with regard to spec compliance, because a specification is a bit different from a software API.