Hello,

Andreas Maunz wrote:
>> To make it short, one POSTs a dataset + parameters  to
>> /algorithm/fminer , and receives the result dataset, where for each
>> feature ot:hasSource points to 
>> /algorithm/fminer/my_new_fminer_instance.
>> The latest encapsulates the dataset+parameters and allows new
>> dataset/compounds to be POSTed to
>> /algorithm/fminer/my_new_fminer_instance , resulting in the dataset with
>> calculated values.
>
> So the complexity of switching modes is hidden inside the
> /algorithm/fminer/ (or any supervised feature selection) service.
> I think it's a good idea, since it solves the problem of feature
> dependency on dataset by controlling that the features are used only
> in the context of specific parameter settings under which they were
> calculated. Nice!
>
>> We already did some brainstorming with TUM some time ago and they have
>> implementation of FMiner to offer URI of descriptors.
>
> What is the URI of this service? If it implements the above
> functionality, I would be interested in using it for different
> purposes. I had a look at
> http://opentox.org/dev/testing/testtoxservices but the information
> seems outdated.

I think it is  
http://opentox.informatik.tu-muenchen.de:8080/OpenTox-dev/algorithm/FTM
, for ambit services have feature entries like  below:

    <rdf:RDF
        xmlns:ad="http://ambit.uni-plovdiv.bg:8080/ambit2/dataset/"
        xmlns:ag="http://ambit.uni-plovdiv.bg:8080/ambit2/algorithm/"
        xmlns:ot="http://www.opentox.org/api/1.1#"
        xmlns:bx="http://purl.org/net/nknouf/ns/bibtex#"
        xmlns:af="http://ambit.uni-plovdiv.bg:8080/ambit2/feature/"
        xmlns:otee="http://www.opentox.org/echaEndpoints.owl#"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
        xmlns:ac="http://ambit.uni-plovdiv.bg:8080/ambit2/compound/"
        xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns="http://ambit.uni-plovdiv.bg:8080/ambit2/"
        xmlns:am="http://ambit.uni-plovdiv.bg:8080/ambit2/model/"
        xmlns:owl="http://www.w3.org/2002/07/owl#"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
        xmlns:ota="http://www.opentox.org/algorithmTypes.owl#"
        xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" >
      <rdf:Description rdf:about="http://www.opentox.org/api/1.1#hasSource">
        <rdf:type
    rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
      </rdf:Description>
      <rdf:Description rdf:about="http://www.opentox.org/api/1.1#units">
        <rdf:type
    rdf:resource="http://www.w3.org/2002/07/owl#DatatypeProperty"/>
      </rdf:Description>
      <rdf:Description rdf:about="http://www.opentox.org/api/1.1#Feature">
        <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
      </rdf:Description>
      <rdf:Description
    rdf:about="http://ambit.uni-plovdiv.bg:8080/ambit2/feature/109768">
        <dc:creator>http://ambit.uni-plovdiv.bg:8080/ambit2</dc:creator>
        <ot:hasSource
    rdf:resource="http://opentox.informatik.tu-muenchen.de:8080/OpenTox-dev/algorithm/FTM3"/>
        <owl:sameAs
    rdf:resource="http://www.opentox.org/api/1.1#TUM_FTM_C%28-c%28%3Ac%28%3Ac%29%29%29%28-c%28%3Ac%29%28%3Ac%28%3An%28%3Ac%28%3An%29%29%29%29%29%28-c%28%3Ac%28-O%29%29%28%3Ac%28-O%29%28%3An%28%3Ac%29%29%29%29"/>
        <ot:units>count</ot:units>
       
    <dc:title>TUM_FTM_C(-c(:c(:c)))(-c(:c)(:c(:n(:c(:n)))))(-c(:c(-O))(:c(-O)(:n(:c))))</dc:title>
        <rdf:type rdf:resource="http://www.opentox.org/api/1.1#Feature"/>
      </rdf:Description>
    </rdf:RDF>

Tobias and Fabian for sure know better :)

Best regards,
Nina

>
> Best regards
> Andreas
>