Does YANG Semver allow two versions with the same X.Y.Z and different metadata?

[jsterne]

We don't allow 3.0.1 and 3.0.1_compatible to both exist.
Should we allow 3.0.1+build11 and 3.0.1+build12 to both exist?

Do we want X.Y.Z to be a complete distinguisher for a module version?

As a corollary: what parts of the YANG Semver would go into the filename?
X.Y.Z?
X.Y.Z_COMPAT?
X.Y.Z_COMPAT+metadata? (could be very long)

[xorrkaz]

A proposal: we state that we ignore build metadata, but our compat identifier and pre-release metadata is used. While names could be long, what if we stick to those for purposes of naming. That is, build metadata is excluded, but compat identifier and pre-release metadata are required for filenaming.