Dear Nina, Martin, All,

It seems yesterdays reply was not delivered to the list. 

> What about combining both solutions?  Features could be in the dataset, as
> in IST services, or as separate resources,  but additionally models provide
> list of predicted variables via /model/id/predicted ?  This way there will
> be still no need of a separate feature service for you.

Problem is that the prediction feature URIs (of the form
/dataset/:id/feature/prediction/:name/{value|confidence}) are built on
top of the dataset URI, which I cannot know in advance. For this reason
new features are created for each prediction. Any ideas how to solve
that without a dedicated feature service? Or would it be easier to
implement a feature service (or use AMBITs) for this purpose (what about
A+A)?

Best regards,
Christoph