If you understand that the "sem" in semver is specifically about semantics and not about anything else, and that an API includes its current semantics in the se

If you understand that the "sem" in semver is specifically about semantics and not about anything else, and that an API includes its current semantics in the semver, then it makes sense. The issues I've struck with other developers: 1. Defining the boundaries of the API 2. Defining the semantics of the API from the perspective of the user