Nested Callback interfaces in View vs Dialog: Android design decision

I was going through the android.view.View and android.app.Dialog classes and I found a striking difference in design of the public interface of the classes. While View has several inner callback interfaces, there is a separate interface for Dialog called DialogInterface which contains several callback interfaces.

My question is, what is the requirement of a DialogInterface to list out the listener interfaces separately. Why couldn't the Android designers have done it like the View class?

Also, is this some standard design pattern?