org.opendaylight.yangtools.yang.binding.YangModuleInfo (as present in md-sal's yang-binding) artifact really belongs to yangtools, or at least yangtools needs an equivalent.

This will allow us to package models in a runtime-discoverable way, without generating MD-SAL binding interfaces out of it. It also provides a Java foothold, which is good enough to extract packaged model's sources while also making sure dependencies are satisfied.

This will allow us to package models and their parser support in centralized bundles, which md-sal can later enrich externally with corresponding Java bindings (or any other bindings, really).

The MD-SAL version also links to imported modules, which creates a strong package-level binding between revisions.

We do not want our version to do that – it should only expose the main module (and its submodules) and metadata about them. Any dependencies will be resolved through parsing anyway.

We also should provide a utility wrapper, which will turn each such YangModuleInfo into a set of model.repo.api.YangTextSchemaSources – which can then be fed into a parser reactor.