FNR Pearl Chair and head of the Software Engineering RDI team at LIST. Also Affiliate Professor at the University of Luxembourg. Leading the BESSER project, an open-source AI-driven low-code platform.
Yes. Ecore could be an easy target as well. We chose UML because it's more well-known (outside the "core" modeling community) but I agree that for people that may want to build their own tools/extensions on top of WAPIml, an Ecore output would make sense.
About the custom notation, we see it as a different path with its own pros and cons (kind of the always on-going discussion about DSLs vs UML).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes. Ecore could be an easy target as well. We chose UML because it's more well-known (outside the "core" modeling community) but I agree that for people that may want to build their own tools/extensions on top of WAPIml, an Ecore output would make sense.
About the custom notation, we see it as a different path with its own pros and cons (kind of the always on-going discussion about DSLs vs UML).