On Mon, 2009-10-12 at 12:21 +0200, Christoph Helma wrote:
> Excerpts from Tobias Girschick's message of Thu Oct 08 15:29:01 +0200 2009:
> > Hi Christoph,
> > 
> > On Tue, 2009-10-06 at 16:03 +0200, Christoph Helma wrote:
> > > Excerpts from chung's message of Mon Oct 05 17:43:19 +0200 2009:
> > > > Dear all,
> > > > 
> > > > In API 1.0, there is no POST for feature selection algorithms. I propose
> > > > the following RESTful operation: 
> > > > 
> > > > ***POST /algorithm/preprocessing/featureselection/{feat_sel_algorithm_id} 
> > > 
> > > I agree in principle, but I would separate the algorithm ontology from
> > > the algorithm webservices (see my proposal for the API 1.1
> > > http://opentox.org/dev/apis/api-1.1/Algorithm), 
> > 
> > I am not totally clear how you envision the algorithm ontology. Here 
> > http://opentox.org/dev/apis/api-1.1/Algorithm you propose that a 
> > GET on /algorithm/{id} returns an algorithm_ontology_uri. Could you
> > specify what I do get back from something like that:
> > 
> > GET /algorithm_ontology/{id}
> > 
> > Would this return the XML (or whatever we choose) representation of the
> > algorithm?
> 
> In principle yes. Another (maybe more intuitive) option would be to get
> the algorithm representation by
> 
> GET /algorithm/{id}: returns algorithm representation

this is definitively more intuitive and basically what's happening right
now. Just the URI is changed/reduced.

> 
> and to use the algorithm ontology to search for algorithms e.g.
> 
> GET /algorithm-ontology/learning/classification: returns URIs for all classification algorithms (or a representation of the the learning/classification subtree)
> GET /algorithm-ontology/preprocessing: returns URIs for all preprocessing algorithms (or a representation of the the preprocessing subtree)

makes sense. We would have to think about, if we return every algorithm
on 
GET /algorithm-ontology 
or if we just return the next URI level. Which would be a little bit
more inconvenient.

> 
> This would require of course, that the algorithm representation uses the same ontology as the algorithm-ontology webservice.

Well, yes, but that's the goal of creating/using an ontology, isn't it.

Best regards,
Tobias

> 
> Best regards,
> Christoph
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
-- 
Dipl.-Bioinf. Tobias Girschick

Technische Universität München
Institut für Informatik
Lehrstuhl I12 - Bioinformatik
Bolzmannstr. 3
85748 Garching b. München, Germany

Room: MI 01.09.042
Phone: +49 (89) 289-18002
Email: tobias.girschick at in.tum.de
Web: http://wwwkramer.in.tum.de/people/girschic