1. Registry requirements Regarding to Web Services and Workflows

2. SOAP and REST  Registry must be able to keep information equally for SOAP and for REST.  SOAP has WSDL language but REST has no standard way for interface specification.

3. Web services relationships  Some relationships between web services must be in the registry. Alternative Web services in case of error Web service mirroring Input/output conversion

4. Collective Intelligence  Registry should keep information about community use for helping CLARIN users on Workflow Creation: “250 users connected these 2 web services in other projects using converter AtoB, do you want to do it as well?”  Also users should be able to rate web services.

5. Web Services development information  Registry should keep information (set manually by users) about new Web service versions -Changes, modifications, improvements-. In this way, users will decide if newer versions of a web services are worthy for them.

6. Some ideas about expected Registry operations  Resource_meta = GetResource(pid)  Resource_meta[] = GetResourcesByCategory(cat)  Resource_meta[] = Search(pattern, sort_by)  Resource_meta[] = GetAlternateResourceTo(pid)  Resource_meta[] = GetSimilarResourceTo(pid)  Resource_meta[] = GetBestRatedResource(cat)  Resource_meta = GetMostGloballyUsedResource(cat)