Where is MDA going to? My personal wish.

Many days ago I published a post about an MDA article , it was about Elaborationist and Translationist approach, and about a “hole” between them. Here it is my personal wish:

1) I'd like to have a computationally complete UML subset for the MDA context;

2) I'd like this subset to be as much general as possible;
3) I'd like to execute and test the models directly.

Having a computationally complete UML subset means that every model has its own semantic, and every model can be an actual part of a system. To define the best syntax for action semantic there is no need to chose between Object Constraint Language and Action Language, the right solution would be to have a mix of the two, defining a resulting language that inherits the best from both the declarative and the imperative approach. I wouldn't like specialised UML diagrams for the embedded systems and other diagrams for the business systems, the models should be domain independent. Does exist a good reason to define specialised UML diagrams with specialised semantic? Domain Specific Languages should be introduced only when really necessary.
I'd like to have the most general models, to exploit abstraction, to keep domain and platform details as near as possible to the end of the model transformation chain.
And finally, I'd like to execute and test models directly, is a key feature for an MDA tool, I don't like to write models and debug Java, C or wathever it was, “I think and write models, and I want to execute and debug modes!”.