Gunnar

> A few questions to you generator: Basically I realize there's a lot to do to make this to the CommonAPI level. It now just produces skeleton code, not really...

Yeah I knew I had an issue with includes, and other things. Thanks for the suggestions. My code is still messy, and the limitations are also not well documented. Awesome...

@thorsten-klein First, thanks for the change proposal. The project’s maintainer/developers seem to be busy with other things and not responding... so the short answer is unfortunately that I do not...

> I have now read this issue, and that did not lead to change of my gut feeling that this does not belong in the VSS data model, but should...

> In VISS the events are represented by "notification messages" that are asynchronously issued by the server when the trigger conditions are met. This is transparent to VSS, which do...

There are several options described in the proposal so it's hard to generalize for all of them. But looking at the simplest most obvious meaning of an event - it...

@UlfBj > For VISS there is no need to define events in VSS Maybe you are still mixing it up with Notification messages here, or you are using VISS as...

@UlfBj > I think that is a key point. Not only to have separate trees, but also to separate the metadata definitions. Parts that are relevant in both can be...

@UlfBj > A large part of the "VSS concept" can very well be used in the "event domain", and sharing on that level I think is fine. But I think...

Please note also that it is a question for the VSC (@magnusfeuer note) whether it really needs the VSC-style events that I described last (that can carry advanced data with...