Hello, There have been a number of SDOs and other groups that were requiring object-oriented constructs in YANG. However we were out-voted.
Myself I am trying to map 3GPP objects to YANG (3gpp TS 32.160 section 6.2 https://www.3gpp.org/ftp/Specs/archive/32_series/32.160/32160-h30.zip). I am trying to find a balance between mimicking object-orientation and keeping YANG readable. It is not always easy. I know that there are similar efforts in ITU and other organizations. Scott may have a full list of such efforts. Regards Balazs -----Original Message----- From: netmod <[email protected]> On Behalf Of Robert Varga Sent: Friday, 25 March, 2022 23:17 To: tom petch <[email protected]>; yuchaode <[email protected]>; '[email protected]' <[email protected]> Cc: Fatai Zhang <[email protected]> Subject: Re: [netmod] [CCAMP][TEAS][NETMOD] Efficiency issues with YANG model data in integration On 17/03/2022 17:32, tom petch wrote: > <tp> > When the data definition language that we know as YANG was being > specified, the question did arise of how object-oriented it should be > and the consensus was that it should not be. Seeking to retrofit such > a concept might be a bit like finding late in the day that the class > definitions that have been chosen do not go high up enough the tree:-( > > An interesting idea but I am not sure how feasible it will prove to be. RFC6095 might be a starting point for that sort of work. I am not sure anybody ever implement that, though. Regards, Robert _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
