Design how to deal with output messages composition

[adrianriobo]

The income message does not really need a fixed structure defined....as the idea is access direct field with jsonpath expression and use them to accommodate the actions.

On the other hand the outcome will transmit a message to a target. So it is needed to think the best approach for handle different message schemas.

• Do they need to be pre defined on code?
  Do we include a set of them depending on the integrations?. How do we make users aware of them?
• Would the spec support inline template definition?
  In this case how to reuse to avoid flooding specs with duplications?

[adrianriobo]

Link to #15

[adrianriobo]

Check some "generic" management based on interfaces... https://github.com/icza/dyno

[adrianriobo]

Also in case need some generation https://github.com/adrianriobo/dater