yang.model.api.SchemaNode is our first cut at modelling YANG constructs. As such it is recognized for its severe deficiencies in capabilities:

• mixed declared and effective semantics
• no way to examine all substatements in order
• clunky extensibility
• assumptions about significant statements (QName, SchemaPath)

These deficiencies have been cured in DeclaredStatement/EffectiveStatement API, which are being slowly adopted.

Drive the adoption process to conclusion, resulting in deprecation and removal of SchemaNode and related interfaces.