1. Creating a new services infrastructure for the European Library Theo van Veen ELAG 2008, Wageningen, 14-16 April The way from sharing data to sharing intelligence

2. Overview Background Vision Demonstration Legal issues

3. Background First ideas were born 2 years ago Actual work started end 2007 as part of Econtentplus framework –TELplus project Workpackage 4 Integration of new services in TEL portal 1.Create a services infrastructure and a schema for service descriptions 2.Identify new services and create a services registry 3.Integrate services in European Library portal 4.Create new services to be integrated in TEL portal

4. The trend Automated library catalogues: search books in a local system Internet: information accessible worldwide via ftp Gopher + Veronica: make information searchable WWW + Google: critical mass created for almost everyone to find almost everything from almost everywhere Web 2.0: share, mix and merge data from users and providers; service providers publish API to their services Expected: Share knowledge about existing functionality (=services) that can be applied (semi-) automatically depending on context in different web applications.

5. Vision for a new services infrastructure There is so much functionality and content available on the web. Individual institutions cannot build all of that themselves and harvest all that content. We have to lower the barrier for using external functionality and content (services). Users see functionality and content elsewhere: we should enable users to select that functionality in combination with local content, without having to write software and even for functionality that is not under local control. We need to describe that functionality and index those descriptions and make that information available to users and other web applications.

6. Some definitions of intelligence (see define:intelligence in Google) Intelligence is a property of mind that encompasses many related mental abilities, such as the capacities to reason, plan, solve problems, think abstractly, comprehend ideas and language, and learn Intelligence is the system's level of performance in reaching its objectives Intelligence is effectively perceiving, interpreting and responding to the environment

7. Perceive, interpret and respond Perceive: –receive data, understand the data format –know how to present the data to the user –offer choices to the user to navigate based on predefined rules Interpret: –know what the results is and offer choices based on context (user preferences, available data or metadata) –Use context to determine presentation and potential new user action Respond: –Trigger new actions (semi-)automatically with the (meta)data as input for a new action: translate, summarize, new search, pronounce, find relations, analyze etc. Learn

8. Receive, interpret and generate new request response replace field analyse replace field (dis)play Drag/ drop (dis)play extract fields XML Sound/ video Search retrieve new request analyse (dis)play trigger by field HTML Web service s

9. Scope: What is a service? Functionality is provided by services A service is any functionality behind a URL resulting in HTML, XML, image, video, text or other data Requests to services are generated by a portal based on context Examples of integration of services: –Deep linking to a service and display or play output –HTTP request to get data and do something “useful” e.g. “summarize” –Use output of a service as input for next service e.g. “translate” and than “convert to speech” –Drag and drop contents of a website in TEL portal, analyze and do new request

10. To: –enable users to search and select services –enable the TEL portal to select and invoke services depending on context –enable the portal to use the output in an appropriate way We need service descriptions Service descriptions can be used to exchange information about services between users and integrators and service providers Services may be described from different perspective for users, integrators and providers as long as they use the same datamodel (link)(link) S chema for service descriptions

11. Service types (taken from IESR) Alert Annotate Archive Ask Authenticate Authorise Contribute Find Harvest Lend Locate Map Monitor Pay Personalise Rate Register Request Reserve Resolve Save Supply Translate Validate

12. Example of service description (not yet based on latest schema) Bablefish http://babelfish.altavista.com/babelfish/tr? service Translate Translate to prefered language by Bablefish trigger>title abstract description urltext HTML POST http://demos.cepstral.com/cepstral/demos/demo.cgi/cep stral.wav?voice=David;rate=170;pitch=1;effect=none;submit=Synthesiz e+the+Text; option replaceField lp en_nl,en_fr,en_de,en_el,en_it,en_pt,en_ru,en_es,nl_en,nl_fr,fr_en,fr_de,fr_el,fr_it,fr_pt,fr_nl,fr_es,de_en,de_fr,el_en,el_fr,it_en,it_fr,pt_en,pt_fr,ru_en,es_en,es_fr

13. Example of service description (not yet based on latest schema) Image annotation http://metis.researchstudio.at/ylvi- telplus/AnnotationController?action=getAll& service identifier identifier:URI identifier:mpeg21 id type=image GET Alert Check for annotations for this object automatic /annotations/annotation alertOccurrences http://metis.researchstudio.at/ylvi- telplus/annotations/annotationservice.html?user=Theo& XML

14. Receive, interpret and generate new request response replace field analyse replace field (dis)play Drag/ drop HTML list alert XML Sound/ video Search retrieve new request analyse (dis)play trigger by field Web service s

15. Example of service description (not yet based on latest schema) Geonames http://ws.geonames.org/cities? service Geospatial Find nearby places spatial:Point _area north south west east XML /geonames/geoname/name createSearchList GET option

16. Receive, interpret and generate new request response replace field analyse replace field (dis)play Drag/ drop HTML list alert XML Sound/ video Search retrieve new request analyse (dis)play trigger by field Web service s

17. Learn When the user is satisfied with the results of a user initiated action the user might want to have these actions performed next time (semi-) automatically The user defines the context and criteria for that action: trigger, conditions and type of action A mechanism is needed to detect, analyze, describe and store the above information A mechanism is needed to share and exchange that stored information with others so that in can be used the next times automatically by different web applications

18. New paradigm Service providers might publish service descriptions via services registries or micro- formats in webpages Users will select and modify service descriptions and store and exchange these services descriptions Users supply their service description to web applications/portals and these applications act accordingly New business models are required when data of providers are used outside the providers context (no branching)

19. Share, exchange and use services descriptions Service provider Microformat in webpage via Google Service integrator user TEL portal Other portal User created Service description Service description Service description Service description Service description Service description Service description Service description Services registry Service description Stored profile

20. Legal issues: TEL can not take legal responsibility for users integrating TEL with “unknown” services TEL can only “serve as a proxy” for trusted parties and providers that give permission for service integration When TEL doesn’t integrate services centrally, browsers won’t allow cross domain access Commercial service providers might not agree with not showing their data in the provider’s context: a mechanism is needed to indicate providers to (dis)agree in a machine readable way We cannot stop users from using services out of their original context (for example Greasemonkey ). Is TEL allowed to provide descriptions for doing that?

21. Monolithic versus service-oriented infrastructure A, B, C Monolithic system CB A Modular system D Modular, components accessible from outside CB A http

22. Schematic model for service integration Service B 4. Modify presentation and add links e.g. to service B Service A 1. Request and response Knowledge Base 3. Lookup metadata and services User agent 2. Interpretation of response from service A 5. Request with output from service A as input Output from service A gets link to service B Description of service B

23. Gateway services for standardization, real integration and cross domain security service 1service 2 gateway URL with syntax Y, HTML output Standardized URL syntax for request, standard XML output URL with syntax X, HTML output Services with the same type but different access