Both these methods are marked as deprecated, as they are a leak from declared to effective model. As such they are only used by MDSAL's binding generator, which does not handle actions nor non-root notifications, as far as I can tell. What exactly is the use case for them?

We have a converter from YANG to YIN (loosely based on YinExportUtils in ODL, but since that was not complete at that time we wrote our own).   That needs to know whether an action is added by augmentation or uses, to be able to regenerate the content of a module properly.

Proper implementation of YIN module export does not actually require any of this. If your implementation requires those bits, they can be derived given the whole-Module visibility, hence I suggest you do that in your implementation, as introducing these methods:

• goes directly against the direction we want to take
• introduces more coupling in yang parser
• adds maintenance burden

Can you clarify then how we can derive that?

For example: isAugmenting() means that either the node has a different namespace (i.e. augment from another module) or there is a corresponding augment statement in current module. isAddedByUses() is similar.