Open abierman opened 2 months ago
I agree with Issues (2) and (3) and think that those should be fixed in the next version of YANG (whatever that is), but I'm not sure about (4).
For (4), I think that it should be handled identically as if the reference was to a definition that simple does not exist. Whether this check needs to be performed when checking an individual module rather than when compiling and validating a schema-set of modules is a different question.
Closing this issue because already covered by #65 and #66
Issue 4 is still open
Since deprecated will mean MUST implement, any current referencing deprecated is just a warning.
IMO since obsolete still mean SHOULD NOT implement, it is also a warning
Summary of changes:
sec 7.21.2
Issue 1) these MUST requirements make a YANG module brittle and hard to change Issue 2) "deprecated" status should be treated as MUST implement, so "current" using "deprecated" is just a warning Issue 3) "obsolete" status should be treated as MUST NOT implement, but it actually is SHOULD NOT implement. Issue 4) use of "obsolete" status should be a warning not a fatal error