[CC-ing NETCONF WG] True. I added those 'must' expressions without error-messages. Error-messages can often times be used to decipher 'must' expressions to a human-readable form. Should we add now? (Note: the drafts are post-LC in the NETCONF WG)
Would anyone be willing to submit a Pull Request to added "error-message" statements for these 'must' expressions? The repos are here: https://github.com/netconf-wg/ssh-client-server https://github.com/netconf-wg/tls-client-server K. // author > On Sep 2, 2022, at 8:40 AM, Sterne, Jason (Nokia - CA/Ottawa) > <jason.ste...@nokia.com> wrote: > > Hi all, > Not many people are going to understand a must statement like that. Maybe a > good idea to also describe this constraint in a description statement > somewhere in the model ? > Jason > >> -----Original Message----- >> From: netmod <netmod-boun...@ietf.org> On Behalf Of Kent Watsen >> Sent: Tuesday, August 23, 2022 9:32 PM >> To: Jernej Tuljak <jernej.tul...@mg-soft.si> >> Cc: netmod@ietf.org >> Subject: Re: [netmod] Must expression: how to test all instances? >> >> Hi Jernej, >> >>> Lada's second example selects everything that does not match a condition >> then states such a selection should return nothing: >>> >>> not(deref(.)/../ts:public-key/ts:public-key-format[not(derived-from-or-self(., >> "ct:ssh-public-key-format"))]) >> >> It works - thank-you! :) >> >> >>> Check if the corner cases work out for your needs, however. Returns true() >>> for >> an empty list, for example. >> >> When the lists are empty, the validation succeeds, which seems correct in >> this >> context. >> >> >>> Jernej >> >> Kent >> >> _______________________________________________ >> netmod mailing list >> netmod@ietf.org >> https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
