Programmatic interfaces to EMBOSS are described below.
The list of interfaces is by no means comprehensive. If you know of other relevant interfaces to EMBOSS please email emboss-bug@emboss.open-bio.org with details.
The available programmatic interfaces include:
Various modules utilise the EMBOSS programs.
http://search.cpan.org/dist/Bio-Emboss/
A Perl interface to the EMBOSS libraries allowing you to write perl programs that look and feel like a typical EMBOSS program.
Bio::Tools::Run::EMBOSSApplicationhttp://doc.bioperl.org/releases/bioperl-1.0.2/Bio/Tools/Run/EMBOSSApplication.html
The EMBOSSApplication class can represent any EMBOSS application. It is created by a Bio::Factory::EMBOSS object which primes it by reading an application ADC file.
Bio::Factory::EMBOSShttp://doc.bioperl.org/bioperl-run/Bio/Factory/EMBOSS.html
The EMBOSS factory class encapsulates access to existing EMBOSS programs.
Bio::Tools::Run::EMBOSSacdhttp://search.cpan.org/~birney/bioperl-run-1.4/Bio/Tools/Run/EMBOSSacd.pm
The EMBOSSacd class represents all the possible command line arguments that can be given to an EMBOSS application.
MOBY is a ontological system for interoperability between biological service providers whether they be data hosts or analytical services. The EMBOSS applications have been incorporated.
http://www.ebi.ac.uk/Tools/webservices/soaplab/overview
Soaplab generates Web Services for command line programs. Two types of Web Services interface (generic interface and typed interface) are possible. The generic interface allows input data to be sent as weakly typed name-value pairs. This allows diverse applications to be integrated under a single programming interface. The typed Web Services interface has input/output type descriptions defined at WSDL/XSD level which allows Web Service clients to check input/output data types using standard means.