Grammar-Extensions

[florianBachinger]

• introduce constant values for e.g. URLs, Paths, or other string values
• node ports are only compatible in their messages if the same messagetype or alias is used. Pattern matching should not be supported.
• add ability to name scopes

Generic-/Standard-Nodetypes

• the restriction for message compatibility requires aliases or casting nodes (e.g. knows which properties to take form a messages and how they should be converted)
• nodes for running AVG, SUM, or other aggregate operations

Message-Quality of Service

• message should include specifiers for the number of executions (e.g. a single message should only be read and computed once (send mail) vs. multiple times (read weather report))

Automated connection of nodes

• introduce an open keyword (name not discussed) to indicate that ports (input messages of a node) are free for automated binding with senders that produce the same message type. This allows the exclusion of explicit mapping code.

Connection of nodes to their implementation counterparts:

• include a version property and identifier to select the actual artefact (Nuget, etc.)