The Nordic Gene Bank, NGB, Alnarp, SwedenThe Nordic Gene Bank, NGB, Alnarp, Sweden

Presentation of Web Services

for theTraining Workshop on

interoperabilityJune 13, 2005 – IPGRI, Rome

Dag Terje Filip Endresen – The Nordic Gene Bank

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 2

TOPICS for this talkTOPICS for this talk

Web Services

Biodiversity data

Standards Data exchange

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 3

Simplicity and global standardsSimplicity and global standards

Important factors behind the success of the web is simplicity and global standards.

A service provider with a web site can reach the global community.

Web services is about expanding the Web as a platform not only to information but also to services.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 4

Web Service definition – W3CWeb Service definition – W3C

A Web service is a software system identified by a URI, whose public interfaces and bindings are defined and described using XML.

Its definition can be discovered by other software systems.

These systems may then interact with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols.W3C, Web Services Glossary[http://www.w3.org/TR/ws-gloss]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 5

Web Service definition - Web Service definition - WikipediaWikipedia

A web service is a collection of protocols and standards used for exchange of data between applications.

Web services provide interoperability between various software applications running on disparate platforms.

Interoperability (e.g., between Java and Python, or Windows and Linux applications) is due to the use of open standards.

Web services easily allow software and services from different companies and locations to be combined to provide an integrated service.

[http://en.wikipedia.org/wiki/Web_services]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 6

Some web service keywordsSome web service keywords

Application-to-application

Platform independent

Programming language independent

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 7

Combination of servicesCombination of services

Web services can be combined to create new services.

Seed bankAccessionInventory

WeatherInfo Service

GIS SpeciesOccurrences

Service

New service to

plan collecting

missions for under-

collected species to a period ofgood

weather.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 8

Some Web Service standardsSome Web Service standards

XML: All exchanged data is formatted with XML, eXtensible Markup Language. The message is transmitted through a transport protocol such as SOAP or RPC.

WSDL: The public interface to the web service is described by Web Services Description Language (WSDL). This is an XML-based service description on how to communicate with the web service.

UDDI: The web service information is published using this protocol. It enables applications to look up web services information in order to determine whether to use them.

[http://en.wikipedia.org/wiki/Web_services]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 9

Example of a web service Example of a web service callcall

All exchanged data is formatted with XML.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 10

Example of a service Example of a service responseresponse

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 11

Message transport protocolsMessage transport protocols

* The message (XML) is transmitted through a service transport protocol such as SOAP or RPC. * And wrapped in a common internet transport protocol like HTTP, FTP, SMTP ... for transport through the internet.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 12

Regular SOAP messageRegular SOAP message

Information intended for the recipient is written in the body. Such as Remote Procedure Call information, XML messages, or error messages.

The header contains additional information on the SOAP message.Such as digital signature information, transaction information, and routing information.

The SOAP envelope consists of a header and a body.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 13

Communication protocol Communication protocol

Although SOAP does not depend on the underlying communication protocol, HTTP is usually used. Because of this, it is possible to communicate with Web services protected by firewalls.

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 14

Data warehouse modelData warehouse model(Slide by Samy Gaiji)(Slide by Samy Gaiji)

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 15

Decentralized modelDecentralized model(Slide by Samy Gaiji)(Slide by Samy Gaiji)

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 16

Network data flowNetwork data flow

Database

Providerwrapper software

Portal

The Data Provider is the web service package (wrapper) installed at the data source.

The Data Portal is a gateway to data published from the data provider nodes.

Provider

etc...

DB

User

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 17

Biodiversity collections dataBiodiversity collections data

Biodiversity collections data have most of their attributes in common, although the terminology used to describe them often differ substantially.

[http://www.bgbm.org/TDWG/CODATA/ABCD-Evolution.htm]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 18

TDWG TDWG TTaxonomic axonomic DDatabases atabases WWorking orking GGrouproup

TDWG Mission:

To provide an international forum for biological data projects

To develop and promote the use of standards

To facilitate data exchange.

The TDWG web site is hosted by The Natural History Museum in London, UK.

[http://www.tdwg.org/]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 19

Biodiversity informatics standards

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 20

Darwin Core 2 (DwC2)Darwin Core 2 (DwC2)

The Darwin Core 2 is a simple set of data element definitions designed to support the sharing and integration of primary biodiversity data.

The Darwin Core is not a sufficient model or data structure for managing primary data, such as a collection database.

Darwin Core can be compared to the MCPD of the PGR community as a minimum common descriptor list.

[http://darwincore.calacademy.org]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 21

ABCDABCD AAccess to ccess to BBiological iological CCollection ollection DDataata

ABCD is a common data specification for data on biological specimens and observations (including the plant genetic resources seed banks).

The design goal is to be both comprehensive and general (about 1200 elements).

Development of the ABCD started after the 2000 meeting of the TDWG.

ABCD was developed with support from TDWG/CODATA, ENHSIN, BioCASE, and GBIF.

The MCPD descriptor list is now completely mapped and compatible to ABCD 2.0.

[http://www.bgbm.org/TDWG/CODATA/Schema/]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 22

PGR sub-unit of ABCDPGR sub-unit of ABCD

PGR

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 23

MCPDMCPD MMulti ulti CCrop rop PPassport assport DDescriptorsescriptors

MCPD is developed jointly by IPGRI and FAO as an international standard for germplasm passport data exchange.

The MCPD is designed to be compatible with the IPGRI crop specific descriptor lists and the FAO World Information and Early Warning System (WIEWS).

The MCPD was first released in 1997.

[http://www.ipgri.cgiar.org/publications/pdf/124.pdf]

The MCPD descriptors are compatible with ABCD 2.0

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 24

IPGRI Crop Specific IPGRI Crop Specific DescriptorsDescriptors

The IPGRI crop descriptors expand the MCPD to meet crop specific needs. As long as these crop descriptors allow for an easy conversion to the format proposed in the multi-crop passport descriptors, basic passport data can be exchanged worldwide in a consistent manner.

The International Union for the Protection of New Varieties of Plants (UPOV) maintains crop descriptors for protection of intellectual property right (since 1961).

The COMECON descriptor lists came even earlier, and was the result of a cooperation of the Eastern European Genebanks in PGR documentation (1949 –1999).

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 25

Biodiversity informatics data exchange tools

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 26

DiGIRDiGIRDiDistributed stributed GGeneric eneric IInformation nformation RRetrievaletrieval

Distributed - a protocol for retrieving structured data from multiple, heterogeneous databases across the Internet.

Generic - a protocol independent of the data retrieved and of the software to retrieve it.

The DiGIR protocol uses the Darwin Core as its data definition.

[http://digir.net][https://sourceforge.net/projects/digir]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 27

BioCASE establish web-based unified access to biological collections in Europe while leaving control of the information with the collection holders.

ABCD is the main data definition used by BioCASE.

Designed generic to handle any schema and connect to any SQL capable database.

BioCASE provide full access to its registry for GBIF. Being a BioCASE provider thus means being a GBIF provider.

[http://www.biocase.org/]

BioCASE BioCASE Biological Collection Access for Biological Collection Access for EuropeEurope

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 28

BioMOBYBioMOBY

BioMOBY is an international research project on methodologies for biological data representation, distribution, and discovery.

MOBY-S is a web service based interoperability solution.

S-MOBY is a Semantic Web-based interoperability solution.

[http://www.biomoby.org/]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 29

Protocol integration - TAPIRProtocol integration - TAPIR

There is a need to integrate the current protocols in use by different biodiversity informatics community networks.

During the TDWG meeting in 2004, the unified protocol was presented and named TAPIR. The TDWG Access Protocol for Information Retrieval.

It was agreed to start testing the protocol by rewriting the data provider software of the existing BioCASE and DiGIR implementations.

Will TAPIR also help us to integrate GBIF with the BioMOBY community??

[http://ww3.bgbm.org/tapir]

Training workshop on interoperability June 13, 2005, IPGRI, RomeTraining workshop on interoperability June 13, 2005, IPGRI, Rome 30

Thank you for listening!