Is there a future for Model Transformation Languages? To be honest, I’m not sure. And I think that this concern is shared by other members of the model transformation community. But of course, maybe we are plain wrong.

I think we can all agree that model transformations and manipulations are a key element in any model-driven engineering approach. The “traditional” way to tackle model transformation problems is to write a transformation program using a specific transformation language (such as ATL, QVT, ETL, …). But my feeling is that this traditional strategy seems to lead us nowhere. On the one hand, I know several companies that prefer to write transformations directly in general languages like Java. On the other hand, semi-automatic approaches (AI-based,  transformation-by-example methods,..) could enable users to generate transformations without actually writing them.

I think this is an interesting and relevant topic to discuss. That’s why I’m organizing (together with Loli Burgueño and Sébastien Gérard) an open discussion* at the next ICMT 2019 conference to discuss altogether whether there is still a future for Transformation Languages. If not, what will replace them?. If yes, how can they remain relevant?.

But to prepare this discussion and make sure it’s useful to all of us, I need your help (even if you won’t be at ICMT; in fact, even more if you won’t be at ICMT). We’ve prepared a very short survey (4-min) to gather some input an opinions on this topic. Please share your thoughts!!

Is there a future for Model Transformation Languages? Answer here: Click To Tweet

I’ll obviously post here the results of the survey and a summary of the session discussion after the event.

* The ICMT page refers to this open discussion as a panel but given that there is only half an hour allocated, we won’t be having formal panelists. Instead, and as explained above, I’ll summarize opinions from the survey and open the floor to any person in the room that wants to participate.

Pin It on Pinterest

Share This