The database of services is available here.
The goal of this database is to keep track of which services are ready to be used in an interoperability context. We define here our understanding of interoperability: A service is considered as interoperable if it can be accessed by a standard protocol. In particular, a service can only be considered interoperable if it can be accessed by another program without human intervention.
In the resource table, we assign three different colors to a given resource:
- GREEN = READY: This means the resource is accessible through a standard protocol, such as SOAP or REST. In particular, a resource cannot be green if it can be reached only via web page or application that requires human intervention.
- YELLOW = POSSIBLE: This means the resource is accessible through a standard protocol, but the resource is tied up to a web page or web application and therefore cannot be used without human intervention. In most cases, making such applications interoperable is an easy step, e.g. by creating a REST service.
- AMBER = HARD: This means the resource has been embedded into a client-server application that assumes the presence of a specific front-end. In this case, making the resource interoperable requires a certain level of redesign of the resource.
- RED = NOT APPLICABLE: This means the resource is either not online or is stored on a media that cannot be accessed straightforwardly, such as a magnetic tape. It therefore requires human intervention, not only on the user side, but also on the server side, for instance by having to ask a person to execute a program not available on-line.