2
Mandate Expose Canadian bioinformatics Web resources in a unified and automatable manner using Semantic Web Services framework. Bioinformatics data and tools will be easier to discover and utilize, and integrate to hasten discovery. First widespread deployment of a grid-framework where the messages are “meaningful” to the machine, and can be interpreted/re-interpreted under a wide range of scenarios.

4
Web Service Adoption The low uptake of modern Web integration frameworks by the bioinformatics community stems from two primary facets: Challenges in implementing these solutions A gap between the abilities of existing technologies and the needs and skills of the target end-user.

5
SOAP Simple Object Access Protocol (SOAP) messaging only successful within well-defined, often project-specific situations. Lack of Semantics" in the Web Service interface descriptions which precludes the automated discovery of appropriate services, and automated pipelining of data between those services.

6
Semantic Web Service (SWS) Achieved modest level of automated interoperability due to limitations in the way the semantics of Web Services are modeled: SWS frameworks are implemented to support legacy data representation frameworks, in particular XML and XML Schema. SWS have annotated XML Schema components describing services based on "meaning" of various input and output fields.

7
Semantic Web Services (SWS) Automating workflow construction and semantically validating the "sensibility" of the connections between services (often referred- to as Schema-mapping) XML Schema is semantically opaque, Applying semantics to it through annotation is extremely limited; – semantically-annotated XML tag can have only one interpretation

9
In transition Data on the Semantic Web is encoded in RDF, while data in most Web Service frameworks is encoded in XML From XML/Schema-based to OWL/RDF-based data representation SAWSDL W3C Rec in 2008 – inputs and outputs of Web Services can be described in terms of ontological models.

10
User Communities (I) End-user community does not usually have a "process model" or "business model" in-mind when searching for a Service. Biologists execute a BLAST alignment NOT because they wish to run a sequence similarity matrix over their input data; BUT because they are interested in finding sequences that are related to their input sequence by homology. Key is the relationships between the input and output data.

11
Bioinformatics Community Needs: New metadata, i.e. Bioinformatics Web Service annotations that describes the biological properties between input and output that are generated by that Web Service.

13
SADI simply comprises a set of standards-compliant conventions and suggested best-practices for data representation and exchange between Web Services that fully utilizes Semantic Web technologies. SADI mandates the inclusion of a single required annotation in the Web Service metadata that describes the biological relationship ("predicate") that is created between the input and output data of that Service

14
SADI Web Service Discovery

15
hasProteinSequence Predicate-based web service invocation. Using the hasProteinSequence predicate in a query automatically invokes a web service capable of obtaining the amino acid sequence for UniProt entry P04637.

16
SADI: Standards-compliant recommendations for implementation SADI consists of several bioinformatics services SADI Services are stateless and atomic. SADI Services consume and provide data via HTTP, POST and GET. SADI Services consume and produce data in RDF format. SADI Service interfaces are defined in terms of OWL-DL classes; – the property restrictions on these OWL classes define what specific data elements are required by the Service and what data will be provided by the Service, respectively. Input RDF data – data is compliant / classifies into Input OWL Class - is "decorated" or "annotated" by the service provider to include new properties reflecting activities performed by the Web Service. Output RDF data – is an instance of the OWL Class that defines the output of the service.

17
SADI Registry Predicate Map

18

19
What can it do ? SADI provides the functionality to automatically and dynamically discover, access, and integrate relevant data from distributed, non-uniform data-sources using disparate ontologies. Key promises of the Semantic Web ! SHARE implementation allows users to query over data that might not exist at the time they pose their query. A query- specific database is dynamically generated as a query is being processed; effectively, the database required to answer the question is automatically generated as a result of the question being posed.

25
Success Criteria Number of Services created/migrated, and their use by consumers worldwide; (Minimum 400 in Canada) Number of software tools created, and their use by third-parties; Number of Canadian HQP trained in construction of Semantic Web Services.

26
Deliverables A fully-documented definition of the SADI Semantic Web Service framework, including submission of this to an appropriate standards body (e.g. OASIS or OMG) A set of core ontologies describing properties and relationships for entities in the biomedical domain A costing-model, for use by future Semantic Web Service providers, outlining the establishment and maintenance costs for the migration from legacy Web or Web Service resources to a Semantic Web Service framework.