>Using semver for an external API is not a good fit at all. Compatibility is binary: it’s compatible or it’s not. Not true. You can be compatible with all APIs

>Using semver for an external API is not a good fit at all. Compatibility is binary: it’s compatible or it’s not. Not true. You can be compatible with all APIs, adding no new features; you can add new features; and you can break existing features. These are the levels that SemVer can communicate. This makes as much sense for a web API as a binary library. >Think on this a bit, and consider how this applies to a service as a whole, and you’ll finally understand what everyone has been telling you. What all 3 of them? A vast majority of people prefer SemVer even if they detest the work that it generates. It's like a form of documentation.