Task Status
This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.
The SWIM service ecosystem is used to:
- understand how the various services, service developments and SWIM Registry relate to each other
- promote harmonisation by identifying opportunities for service definitions
- promote harmonisation through the use of services in multiple contexts
- promote harmonisation by identifying shared characteristics between services (e.g. service categories, standardised implementations)
- enable more efficient service developments by making relevant artefacts available
Activities:
- start to document the service ecosystem. This will aim to build an aggregated picture of the services based on on actual services. This can e.g. be used to spot dependencies between services.
- categorise the services
- understand the role of the registry and its processes in the ecosystem
Three areas of work compose the Service Ecosystem:
- Service Sources: Any source of services that could be explored to find new or updated candidate services.
- Service Developments: Any activity developing a service description or service definition or service overview.
- SWIM Registry: The European SWIM Registry is the target repository for SWIM services in Europe.
Child pages: