# Semantic Versioning **URL:** \ **Category:** Spec\ **Created:** [September 11, 2014, 9:38pm UTC](https://talk.commonmark.org/t/semantic-versioning/567 "2014-09-11T21:38:28Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Burt\_Harris](https://talk.commonmark.org/user_avatar/talk.commonmark.org/burt_harris/32/368_2.png) [@Burt\_Harris](https://talk.commonmark.org/u/Burt_Harris)\ **Post date:** [September 13, 2014, 1:10am UTC](https://talk.commonmark.org/t/semantic-versioning/567/2 "2014-09-13T01:10:55Z")
Interesting idea, but Semantic Versioning is defined in terms of API compatibility. For CommonMark, I think the much more pressing question is about versioning the specification. For example, in topic [What is the point of limiting uri schemes in autolinks?](http://talk.commonmark.org/t/what-is-the-point-of-limiting-uri-schemes-in-autolinks/555/10) I’m proposing a change to the specification that makes it simpler and more consistant. But it changes the result of one of the specified test outputs, sort of a corner-case one at that. Technically speaking, my proposed change would have no impact on the API of an implementation, but it does change the expected output in a _slightly_ non backwards-compatible way. How do you apply semantic versioning to that? --- _[View the full topic](https://talk.commonmark.org/t/semantic-versioning/567)._