We discussed this, and I opted for “version” for two reasons. One, the prefix is included (it’s now just “ys” for simplicity), and two, ultimately, we want to give YANG modules (and later packages) a “version”. The “semantic” modifier in the typedef name feels like needless extra typing since you would refer to the base anyway to understand the normative properties.
Additionally, we moved away from revision-label since we are no longer introducing multiple schemes. You might want to consider changing your leaf name to something echoing “version”. Joe From: Benoit Claise <[email protected]> Date: Friday, May 31, 2024 at 12:11 To: [email protected] <[email protected]> Subject: [netmod] draft-ietf-netmod-yang-semver: version or semantic-version Dear all, Looking at https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-yang-semver-12&url2=draft-ietf-netmod-yang-semver-13&difftype=--html, we went from revision-label to version [cid:[email protected]] We used this field in draft-ietf-netconf-yang-notifications-versioning leaf revision-label { type ysver:version; description "This references the YANG module semversion to be sent in the subscription."; } } One question: why not have a better name directly in draft-ietf-netmod-yang-semver<https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-yang-semver-12&url2=draft-ietf-netmod-yang-semver-13&difftype=--html>, which we could reuse? For example: semantic-version Regards, Benoit
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
