In such an environment, there is an increased need for techniques that help make sense of the highly heterogeneous and dynamic service landscape. In this regard – rather than prescribing standards, in the hope of them being adopted – we privilege approaches that, bottom up, observe the state of deployed services and attempt to describe them in the best possible way. Such approaches are less vulnerable to becoming outdated or being neglected by the developer community.
Rather, they allow developers to follow their individual, domain-dependent style of designing and exposing services. We adopt the principle that commonalities between services should be discovered rather than enforced. Diversity needs to be considered, but should also be embraced.