The way we specifies it in the current draft means that every incompatible change would increase the version number of a specification and thus for all included capabilities. This would be really awkward if it results in capabilities v2, v3, etc. that are all identical.
I am not sure if we will ever need per-capability versions and I sure hope we will not, but I wanted to address this issue in some way.
This might also help decide how to "slice" provider specifications. If one specification includes capabilities that are likely to evolve independently of each other, this might warrant putting them in separate specifications.
The way we specifies it in the current draft means that every incompatible change would increase the version number of a specification and thus for all included capabilities. This would be really awkward if it results in capabilities v2, v3, etc. that are all identical.
I am not sure if we will ever need per-capability versions and I sure hope we will not, but I wanted to address this issue in some way.
This might also help decide how to "slice" provider specifications. If one specification includes capabilities that are likely to evolve independently of each other, this might warrant putting them in separate specifications.