Hi, I asked about this text on page 156:
In statements that have any data definition statements as substatements, those data definition substatements MUST NOT be reordered. I asked why this new rule was added. I do not see why it is needed, or how it can be enforced. If I add a new object to grouping A, then every place there is a "uses A", a new data node will be inserted inline. If I add a leafs at the end of a nested list, it is before the data nodes following the list. Does this text mean one can never reorder the data nodes, such that the relative order never changes? Or does it mean new objects must go at the end of a module? Why do we think it is user-friendly to force statement order to be a critical one-try-or-else decision? What happens if the original statement order was a mistake? Is this allowed to be corrected in a future version? Why is this text required for YANG to be interoperable? Given that all nodes are QNames, this rule is not needed. (I don't care about some corner-case XPath functions that the YANG guidelines already say not to use.) Andy
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
