Re: [netmod] definition of "fully expanded YANG"

[Juergen Schoenwaelder <[e-mail]>]

On Wed, Jul 17, 2019 at 01:18:57PM +0000, Michael Rehder wrote:
> Yes, inlining of everything, including augments. What you'd see in the tree representation.
> For example augments makes it particularly impossible for a consumer of the YANG schema to process the schema since the final result.
> 
> Some use cases:
> - translating to another schema language
> - translating to a UI dialog for data entry
> - an accurate diff on versions
> 
> Model-driven-design means using the "computable specification" for all sorts of things, increasing the ROI of the schema definition.

It sounds to me like you are interested in what compiler people call
the abstract syntax tree, which is quite a different thing than the
YANG module you start with. The easiest and most robust way to do
translations is likely to simply expand pyang (or any other compiler
of choice).

> The diff is a significant issue. As a schema author, I must reliably document all changes.
> Without a full expansion, it's easy to not notice that a particular module has changes in its final form.
> I don't see how you could verify a semantic version number in a package without this.

Well, this sounds a bit like a tooling issue. You are likely better
off with a tool that can do a semantic comparison for you instead of
working with "fully expanded YANG" modules and generic diff tools.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>