Kent Watsen <[email protected]> writes: > Hi Lada, > > I agree that there is a close alignment but then I guess NETMOD should have > started with a different approach, perhaps object-oriented rather than > document-oriented, where configuration could play the role of "methods" > intended for changing the object's state. (If Randy Presuhn was reading this, > he would probably refer to certain ancient technologies at this point.:-) > > <KENT> I just added https://github.com/netmod-wg/yang-next/issues/25. Note, > this would definitely be in a YANG 2.0 (if done at all), as oppose to in a > YANG 1.2.
I suspect it would have very little in common with YANG as we know it, but I am not suggesting to start such work - my point is that the config/state schema unification tries to fit a round peg in a square hole. > > > > It is quite remarkable that formalisms closely related to YANG (W3C XML > Schema, RELAX NG/Schematron/DSDL, XPath) were all initially relatively simple > and elegant (albeit limited) and became popular, but subsequent > consortia-driven "improvements" made them so complex that nobody understands > the new versions any more, and only the old versions remain in use. I am > concerned that YANG is now bound to the same path. > > <KENT> This is an important point. Perhaps you're saying that it's better for > us to obsolete/cannibalize ourselves than passively waiting for it to > happen. Not really, what I am saying is that it may be wiser to accept limitations of YANG architecture instead of stretching it too far. I agree that foo and -foo state duplicity is suboptimal but I think it is not THAT bad. In terms of NMDA, I can imagine that schema for configuration datastores and <operational> be specified separately. > FWIW, in terms of complexity, I think that schema-mount in particular has > pushed the YANG-complexity envelope more so than any other recent > activity. I fully agree and I have said it myself several times. My concern applies to schema mount as well. Lada > > > > -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
