Hi, We reviewed draft-ietf-netmod-yang-semver-24.
Issue (interop): the YANG typedef/pattern for ysv:version appears more restrictive than SemVer, while the document states that a SemVer version number is legal according to the YANG Semver rules. In particular, the current prerelease portion requires ending with '.' or '-' followed by digits (i.e., "...[.-][0-9]+"), which rejects valid SemVer such as "1.0.0-alpha". Impact: common SemVer strings produced/validated by standard tooling will fail YANG validation, leading to divergent behavior across implementations and breaking downstream conventions that carry ysv:version (e.g., filenames). Proposed change: align the prerelease/build syntax with SemVer 2.0.0 structure (dot-separated identifiers), while keeping the optional "_compatible"/"_non_compatible" suffix as defined by this draft. One compatible structure is: - prerelease: (-[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)? - build: (\+[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)? Thanks, Meir Goldman FAZON Foundation [email protected] https://fazon.org
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
