Surajit,

Please have a look at my recent examples - I think they do what you need
within the current API.

Best regards,
Christoph

Excerpts from surajit ray's message of Mon Nov 22 14:44:34 +0100 2010:
> Hi Nina,
> 
> So the new DataEntry (or subclass) will have multiple compounds and
> single feature assigned to them ?
> 
> Regds
> Surajit
> 
> On 22 November 2010 14:27, Nina Jeliazkova <jeliazkova.nina at gmail.com> wrote:
> > Hi Surajit,
> >
> > Obviously we should introduce multi entity relationships, I am trying to
> > figure out what's the most appropriate way and how other ontologies manage
> > this case.
> >
> > Looking again at opentox.owl, it seems we only need ot:DataEntry (or
> > subclass of it)  to allow more than one compound , there is no need to
> > assign features to datasets and mess with changing datasets.  This way there
> > will be no need to have "fake" datasets of two compounds just to represent
> > MCSS between two structures.
> >
> > Best regards,
> > Nina
> >
> >
> >
> > On 18 November 2010 10:13, surajit ray <mr.surajit.ray at gmail.com> wrote:
> >
> >> Hi Nina,
> >>
> >> Are we allowing features to be assigned to datasets in the next API
> >> iteration ? It would greatly enhance the APi as there is no way of
> >> having multi entity relationships at this moment. As to the datatset
> >> integrity - we can assure it using the A&A ....
> >>
> >> Surajit Ray
> >> Research Associate
> >> JNU
> >> _______________________________________________
> >> Development mailing list
> >> Development at opentox.org
> >> http://www.opentox.org/mailman/listinfo/development
> >>
> > _______________________________________________
> > Development mailing list
> > Development at opentox.org
> > http://www.opentox.org/mailman/listinfo/development
> >