[OTDev] ToxCreate integration of Ambit classification datasets
Christoph Helma helma at in-silico.chWed Mar 23 13:25:00 CET 2011
- Previous message: [OTDev] ToxCreate integration of Ambit classification datasets
- Next message: [OTDev] ToxCreate integration of Ambit classification datasets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nina, > > If you look at /dataset/9 RDF representation, there is ot:acceptValue in > RDF representation, which lists possible values for the feature. This was > agreed for API 1.1 and is in the opentox.owl , and is used by TUM/NTUA > services as far as I know. > > <http://apps.ideaconsult.net:8080/ambit2/feature/21573> > a ot:Feature , ot:NumericFeature , ot:NominalFeature ; > dc:creator "http://www.epa.gov/NCCT/dsstox/sdf_isscan_external.html" ; > dc:title "Canc" ; > ot:acceptValue "3.0" , "1.0" ; > ot:hasSource < > http://apps.ideaconsult.net:8080/ambit2/dataset/ISSCAN_v3a_1153_19Sept08.1222179139.sdf> > ; > ot:units "" ; > = otee:Carcinogenicity . > > I would suggest modifying your implementation to use ot:acceptValue, instead > of regexp. Oops, I forgot about this one. Is ot:acceptValue ordered, i.e. can I trust, that the first value indicates always true/active and the second one false/inactive? Best regards, Christoph
- Previous message: [OTDev] ToxCreate integration of Ambit classification datasets
- Next message: [OTDev] ToxCreate integration of Ambit classification datasets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Development mailing list