iHOP Web Services

iHOP provides web services in two flavours: CGI-XML (like DAS servers) and SOAP web services

• CGI-XML

  The basical iHOP functionality is available through five different CGI services. Sample forms are available:

  • getRelatedSymbols, which returns a list of the available iHOP symbols which can be the one you have typed in
  • getSymbolInfo, which returns some information about a gene symbol
  • getSymbolDefinitions, which returns the sentences that iHOP used to define the input symbol
  • getSymbolInteractions, which returns the sentences which are describing an interaction with other gene symbols
  • getPubMed, which returns a iHOP digested abstract from the input PMID

  These CGI services usually take as input parameter either the gene symbol or the corresponding iHOP ID. There are two exceptions: getRelatedSymbols, which only takes as input parameter a gene symbol; getPubMed, which takes either a PMID or an iHOP PMID. The generated output is in XML. When the requested information is not available, the CGI services use the standard HTTP code 404.

• SOAP Web Services

  The same functionality above described is available as a SOAP web service. This web service has as many ports as the previously described CGI services, and their outputs are based on the XML Schema above introduced.

  One of the advantages of SOAP services is that they can be integrated in workflows designed by tools like Taverna.