1. Web Services Interoperability Through Standardisation The EMBRACE Technology Recommendation

2. Why Use Web Services In The First Place? Interoperability

3. Service Oriented Architecture (SOA) Functionality is most commonly expressed as services. Each service provides one clearly defined basic functionality. Higher level functionality is achieved using service composition.

4. Web Services Interoperability organisation Initial Web Service specifications were quite flexible –Many different ways to make Web Services –Hard to make tools that could be used for all types of services Web Services Interoperability organisation was founded to establish more restrictive specifications –Similar services –Outdated tools

5. The Evolution Of Web Services

9. SOA Is Becoming Boring  Has become part of the software industry SAP Oracle IBM Microsoft

10. SOA Is A Part Of Society  Applications in Norway: All parts of government Police Major hospitals Companies

11. The Technology Recommendation: An EMBRACE of WS-I WS-I is ready (ish) to use Many tools and supporting technologies available Competence is available

12. A closer look at Web Services XML

13. Client WSDL File Web service Usage scenario

14. Client WSDL File Web service Client reads the WSDL file

15. Client WSDL File Web service Client sends request

16. Client WSDL File Web service Client receives the response

17. Extensible Markup Language A way of structuring information Use Elements and attributes...

18. XML Schema Schema Instance John Doe 40 Person First Name Last Name Age Class Person John Doe 40 Object

19. XML Binding Representing the information in an XML document as an object in computer memory John Doe 40 Person John Doe 40

20. Namespaces Avoids naming conflicts We can use prefixes for shorter notation...

21. SOAP –The protocol formerly known as “Simple Object Access Protocol”  The SOAP Envelope for messages  Processing model for how to deal with the messages  Protocol binding framework

22. SOAP Message Or just:

23. Web Service Description Language –Provides an abstract definition of a Web Service and a binding which ties it to a concrete endpoint. –Is completely independent of the Web Service it describes.

24. WSDL file XML Schema definitions of data formats Definition of messages for input and output of the operations in this service. Definition of the operations available at this service. The binding of the operations to a set of protocols. SOAP over HTTP is most commonly used Name and network address of this service

25. Schema part of a WSDL..............

26. Corresponding SOAP message MA0003 PFM CORE

27. Sample Perl Client my $wsdl = XML::LibXML->new->parse_file('http://api.bioinfo.no/wsdl/JasparDB.wsdl'); my $proxy = XML::Compile::WSDL11->new($wsdl); my $getMatrixById = $proxy->compileClient('getMatrixById'); my $answer = $getMatrixById->( Id => $get_by_id, Format => $format, Database => $db ); my $matrix = $answer->{parameters}{Matrix}; _print_matrix($matrix);

28. eVita Project Norwegian research council eScience program Has funded a 2.3 me project to build a SOA to support systems biology research at BCCS. Built with WS-I Web Services Partners in UK –MyGrid –Manchester Interdisciplinary Biocentre

29. EuTRACC The European Transcriptome, Regulome & Cellular Commitment Consortium Aims to identify TFs and interacting partners expressed in neuronal and haematopoietic cell types. European NoE Primarily partners with biological competence Lenhard group responsible for analysis

30. EuTRACC tasks Integrative analysis of proteomics, gene expression, chip-chip and chip-seq data Determine the principal regulatory network components Build supporting infrastructure –Performed by the eVita project

31. IRC The International Regulome Consortium –The discovery of how gene function is regulated in mammalian cells during development –Collaborates closely with EuTRACC –Will use same/simmilar infrastructure

32. Jaspar Database Database of profiles of transcription factor binding sites Prediction of over-represented TFBS i sets of genes Statistical analysis

33. Steps forward in EMBRACE Define common data types Links to ontologies

34. Acknowledgements Vincent Breton Jean Salzemann CNRS /Clermont-Ferrand All other members of the Technology Recommendation and Watch WP Steve PettiferUMAN Inge Jonassen Pål Puntervoll Rein AaslandBCCS Toby GibsonEMBL