Semantic validation of the routing file

We already validate the routing file against an XSD schema for syntactical correctness but we could also validate it in a semantical way, e.g.

* Detect multiple usages of the same command from different endpoints
* Validate the specified messages against the configured conventions to detect wrongly configured messages/events (e.g. handling an event as a command)
* ...more ideas?