You are here: Home » Development » API » API 1.1 - archived version » Feature


— filed under:

Feature (former Feature_definition)


Component description

A Feature is an object,representing any kind of property, assigned to a Compound. The feature types are determined via their links to ontologies (Feature ontologies, Decsriptor ontologies, Endpoints ontologies)

REST operations


Description Method URI Parameters Result Status codes
get description of a specific feature definition GET /feature/{id} - URI-list  or RDF representation of a feature
create a new feature
POST /feature
Content-type="any-of-RDF-types", content=RDF-representation
URI of the new feature definition 200,400,404,503
update feature
Content-type="any-of-RDF-types", content=RDF-representation -
delete feature DELETE /feature/{id} -
get a list of available feature definitions

URI list or RDF of features found by the query or all available, if query is empty

Returns all features, for which owl:sameAs is given by the query

HTTP status codes

Interpretation Nr Name
Success 200 OK
No feature found, or specific featurenot found 404 Not Found
Incorrect parameters 400 Bad request
Service not available 503 service unavailable


RDF representation

Feature and FeatureValue class in opentox.owl


Note: Extension of opentox.owl with a subclass of ot:FeatureValue (e.g. ErrorValue or something alike) to denote the case of failure/reason for failure.  FeatureValue is composed of feature and value, where the feature will point to what calculation has been attempted (including the algorithm) and the value itself can be string with human readable description of the reason of failure, or URL.

Document Actions

Extension for Atomic Features

Posted by Barry Hardy at Mar 12, 2010 09:31 AM
We need extension to the API to cover atomic features such as charge, polarizability, tautomeric states, metabolic susceptability etc.