Features should be able to know what their Reporter is. The model
currently has no way to navigate from a Feature to its Reporter

Discussion:
Raise by Michael Dondrup 10/2/02

"Given a particular Feature (eg. by selecting a spot on a image of an
array), try to retrieve data for the BioSequence via its Reporter. I
would suggest a direct association from Feature to Reporter. Or is this
only adding redundancy to the model?'

Reply from Paul Spellman 10/4/02

"there is a very good reason for this association not to exist.
Features are immutable and confined to a single array, Reporters are
flexible and can be present on multiple arrays. Requiring Features to
know which Reporters they are in could in some cases be a logistical
nightmare.

This is best solved using a database query rather than the model."

Reject the change.

The association ExperimentDesign should be
Experiment(1..1)-->ExperimentDesign(1..n)

instead of

Experiment(1..1)-->ExperimentDesign(1..1)

and the association name and end role should become 'ExperimentDesigns'
and 'experimentDesigns'

Discussion:
Raised by Angel Pizarro 9/9/02 and requested by the Ontology Group

see below

BibliographicReference needs to be able to point to multiple
database entries. An association will be added between
BibliographicReference and DatabaseEntry which will be named 'Accessions'
with the end role name of 'accessions' on the DatabaseEntry end. It will
be navigable from BibliographicReference to DatabaseEntry and its
aggregation
will be of type composite. The cardinality of the BibliographicReference
end will be 1..1 and the cardinality of the DatabaseEntry end will be 0..n

see below

The rule in the ExperimentDesign package that only allows a single
FactorValue per TopLevelBioAssay hinders proper description of
multi-channel experiments and should be dropped

Discussion:
Raised by Angel Pizarro 3/4/03

"During the MGED Ontology workshop, we came across a situation that does
not allow you to describe certain ExperimentDesigns. For instance in a
loop design, you compare conditions A,B,C as follows:
A -> B
B -> C

If A,B & C represent different values of the same ExperimentalFactor, how
do you encode that a single top-level BioAssay is A -> B? Remember that
there is a Rule in the ExperimentDesign package that states that each
TopLevelBioAssay can only have a single FactorValue per
ExperimentalFactor."

Reject the Change

The MerckIndex association between Compound and OntologyEntry is too
specific. The association should become more general and allow more
than one kind of Index. The name of the association and end role will
change to 'CompoundIndices' and 'compoundIndices' and the OntologyEntry end
will change its cardinality to 0..n

see below

The Type association between BioSample and OntologyEntry needs to be
optional.
The cardinality of the OntologyEntry end will change from 1..1 to 0..1.

see below

Discussion:
A draft was created by Cathy Ball and her group that is included
as a separate document

Issues:
The changes were done on a previous version of the standard and
need to be merged to the available standard

The changes need to be backed merged into the UML model to keep
the documentation in synch in the generated DTD and code.

no action taken