A number of places in mdsal-binding-api are using yang.binding.InstanceIdentifier. With MDSAL-815 we have replacement constructs, which better model the intent of the user.

Services in the following manner:

• ReadOperations: new read()/exists() methods which take binding.api.InstanceIdentifier
• WriteOperations: new put()/merge()/delete() etc. methods which take binding.api.InstanceIdentifier
• DataTreeChangeService: two new registerDataTreeChangeListener() methods, one which takes binding.api.InstanceIdentifier and one which takes binding.api.InstanceWildcard. Note that instead of DataTreeIdentifier these should explicitly take a LogicalDatastoreType

Furthermore, DataTreeModification needs to be updated to render getRootPath() deprecated:

interface DataTreeModification<T extends DataObject> {
  @Deprecated
  default DataTreeIdentifier<T> getRootPath() {
    return DataTreeIdentifier.create(datastore(), rootPath().toLegacy());
  }

  LogicalDatastoreType datastore();

  InstanceIdentifier<T> rootPath();
}