Jordi Cabot

It's indeed not supported (except for some internal artefacts as the metamodel that @hamzaed mentioned above, but there is no full pipeline that integrates them with the rest of the...

I take your point on the need for better alignment between our metamodel and the documentation. We could indeed write a transformation from our Ecore metamodel to a "pure" UML...

Thanks for the contribution. This feels more like a separate project that we could add under the organization umbrella. Let's talk about it in our next meeting

I don't think we were able to replicate the problem. And with now having InfluxDB as another alternative, I'd close it for now (at least until the issue reappears and...

Got the error again. It can be fixed by removing the file analytics.db (of course then you lose the data there). It seems the error happens depending on how you...

I'd just close the issue. Given that we have the influxdb option and the "no monitoring" option (to be added to the wiki page of properties, if not yet there),...

It seems that this one: val whereDoYouWork = intent("Where do you work?") .trainingSentence("Where do you work?") .trainingSentence("Where are you located?") .trainingSentence("Where is your office") .trainingSentence("Where can I visit you?"); is...

This is the same approach that nlp.js used. And I agree it's good enough for a first phase. We don't want to try to go for a perfect solution

Moreover now it can be implemented via the LLM intent classifier

Let's keep in mind that the solution needs also to be language-dependent (and must not throw an exception when using the framework with a language for which no spell-checker solution...