Dear Pantelis, All,

chung wrote:
> However...
>
> * When building a new model, the service has to generate a new feature
> that will be used as a pointer to the predictions made by this model. Is
> this operation implemented?
>
>   
Provided we don't have currently API for creating new features (these
are more or less embedded in datasets), there are two options I can
think of:

1) Extend the API to include Feature creation (independent of a
dataset), e.g. /feature POST rdf-representation-of-a-feature  (similar
to feature_definition POST in API 1.0)

2) Embed the RDF representation of the new feature into the RDF
representation of the dataset, which is then POST-ed to a dataset service. 

e.g. if a feature is described with triples  and there is no feature
URI, the dataset service will assume a new feature is to be created;

In fact the two options are not mutually exclusive, with the first more
generic and the later requiring a single POST call to the dataset
service, instead of two (one for feature creation  and one for posting a
dataset).

Are there any preferences?

> * When a client posts a dataset on a model to make a prediction, then
> the service generates a new dataset which (according to the API) should
> be posted to a dataset service. Is this operation available?
>   
ambit services accept SDF datasets on POST currently, and RDF upload
will be available later today (if everything works right).
> * How can I calculate a feature value for a certain compound URI? Is
> there an example (e.g. curl command)?
>
>   
Perhaps we need "compound_uri" parameter for algorithm API, similar to 
Model API ?   

AFAIK TUM are developing descriptor calculation service, it will make
sense to synchronize parameter names.

Hope this helps,
Nina


> Best Regards,
> Pantelis
>
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
>