Final Report of Working Group 5Interoperation.ppt

Final Report of Working Group 5Interoperation G. Simons (chair), H. Aristar-Dry, D. Iannucci, E. Richter, H. Sicard,  N. Thieberger, P. Wittenburg ELIIP Workshop, Salt Lake City, 12-14 Nov 2009 Interoperation What is it? Interoperability is the ability for two or more systems to exchange information or services and to make satisfactory use of what is exchanged. What does it take for this to happen: The systems agree on standardized definitions of the concepts about which they want to share The systems use a standardized format and protocol for information interchange Why interoperate? It prevents a centralized service from duplicating the efforts of others It maximizes data freshness since updates are propagated when made by the owner It makes a centralized service more sustainable since others bear the cost of providing data It allows multiple centralized service to add value to the same basic information Ways to build a web information service Centralized database curation The service is self-contained: the service defines the database, users edit the data directly, the service curates the information Centralized database aggregation The service has no data of its own: it uses an interoperation protocol to populate the database from other sources that curate the desired information The hybrid approach The service uses an interoperation protocol to aggregate all information it can get from elsewhere. The service develops a database to handle new information it will curate (whether missing data or alternative values). As a “good citizen” the service shares its unique data with others via the same protocol. End users see a combination of the aggregated and the curated data. What does this mean for ELIIP? For each kind of information that the centralized ELIIP service wants to offer, it must decide whether to: Aggregate it, Curate it, or Do both The answer can be different for different kinds of information What kinds of information? Web pages a