Version 5 (modified by mccarthy, 14 years ago)


Day 1: SADI Web Services

We are beginning to publish a set of best practices for service providers by codifying the lessons we've learned in the last year of service-building.

For example, say we have a service 'getKEGGParalogsByGene', which will provide the KEGG ID of the paralogs of any input KEGG gene id. The output class would be defined as in the ontology below:


<!-- Ontology Information -->
<owl:Ontology rdf:about="">
    <owl:Ontology rdf:about=""/>
    <owl:Ontology rdf:about=""/>

<owl:SymmetricProperty rdf:about=""/>

<owl:Class rdf:about="">
   <rdfs:subClassOf rdf:resource=""/>
          <owl:onProperty rdf:resource=""/>
          <owl:someValuesFrom rdf:resource=""/>


The important things to note are:

  1. we are explicitly importing any ontology we refer to
  1. our output class is a subclass of the input class (in this case, a KEGG_Record)
  1. our output class includes a restriction indicating that the service returns KEGG_Records related to the input by the 'isParalogOf' predicate (i.e.: KEGG_Records that are paralogs of the input KEGG_Record). The owl:valuesFrom property on the restriction allows us to do reasoning about how to chain services together. It is important that we put this restriction here instead of in the owl definition of the predicate itself, since it allows us to constrain OUR use of the predicate, without constraining its range for anyone else!

The SADI Taverna plugin has been updated to use the information in these restrictions for service discovery.