clearer I/O relation between Process and I/C/E
this PR IMO simplifies Input/Output relationships between Processes and Intents/Commitments/Events
Instead of relying on interpretation of 'action verb' the which relates Intent/Commitment/Event to a Process itself captures the input/output aspect.
Since we consider defining service as Intent/Commitment/Event which can reference two processes
- one as outputOf
- other as inputOf Approach below makes it possible, since in case where we need to relatet I/C/E to two processes we can't just rely on 'action verb'.
Not sure if we need distinct properties for Intent, Commitment and Event or enough to just have inputOf & outputOf and rely on the type of instance using them to make distinction between Intent, Commitment and Event expressing Inputs and Outputs.