YANG parser currently does not completely buy into the entire DeclaredStatement vs. EffectiveStatement object model. While we expose proper model in some cases, like implied case/input/output statements, there are other places where we still let the SchemaNode object model be the primary or we leave much for users to reinvent.

Notable omissions include:

• EffectiveConfigStatement being added/removed based on instantiation context
• EffectiveStatusStatement being added based on instantiation context
• EffectiveRevisionDate being added based on import linkage

Identify such gaps and arrange for them to be closed.