			APT Data Model Design Review Minutes		3/27/01
			------------------------------------		-------

Proposal is a loaded term. Let's use the term "Proposal Specification" for the APT
document that a user is creating with APT.

Data must be stored in the format that it is entered to preserve the user
representation of that data when it is re-displayed.

Tools may want to notify the built in APT tools (i.e. the hierarcichal and spreadhseet
editors) of state in order to change some aspect of their display.

The model should include pattern expansion data. (i.e. POS TARG info from Trans).

There is data common to both Observations and Exposures. We should break this out into
an object that is shared between phase1 and phase2 (i.e. observations and exposures).

Data will be required to communicate Trans derived value to SPIKE (replacing the 
current TIC file interface).

Are we mixing up the proposal specification with the non-proposal spec persistent,
and the transient data? 

We appear to have four categories of proposal specification data:

1. User supplied proposal specification data.
2. Persistent data derived by one tool that should be shared among tools.
3. Transient data derived by one tool that should be shared among tools.
4. Tool specific data (which would be persistent by definition).

We need a clear mechanism for deciding what data falls into which of the four
categories.

VTT:
----

We may need to store the following:

* background image for an exposure.
* color maps are tied to a background image.
* inclusion and explusion points.

There are tool settings that may be tied to a specific context.

Do we want to provide a generic mechanism for tools to attach their own data to an
object in the proposal. [Yes: this is item 4 in the list above].

We may need higher level attributes (e.g. virtual apertures, science mode and 
coronography).

ETC:
----

Changes:

* Add emission lines.
* Add background information.
* Break information out of the exposure object.

It is not clear which parts of the data model are generic and which are HST specific. We will look
for generic classes and break them out from the HST specific code when possible.

					-----------

We will mail out a specific request to the APT tool developers to look at the details
of the data model.
