[QUANTITY] Data Model for Quantity v0.5

[Brian Thomas]

On Tuesday 11 May 2004 06:39 am, David Berry wrote:
> >  (2) You want to change add/remove/getValueQuantity
> >                      to add/remove/getAlternativeValue.
> >
> >   I don't have a big problem with this.
>
> Is this simply a name change? If so, I suppose I do not see it as a show
> stopper. But I think the current names describe what is going on quite
> clearly - we have
>
> add/remove/getCoordsQuantity

	Since these are essentially "quantities which describe how to access
	another quantity" what about "AxisFrame"? [hurm. I know thats not a
	stellar name either..]

>
> for accessing the various coordinate systems which can be used to describe
> positions within the enclosing Quantity. So it seems symetrical to
> also have
>
> add/remove/getValueQuantity
>
> for accessing the various data value systems which can be used describe
> values in the enclosing Quantity. Can Brian remind us why he suggests the
> change (afraid I've lost the original message in the flood).

	Hmm. The more I think about it the less I like any name. I guess not changing
	is better than changing, so I will shut up on this until I can think of a brilliant
	renaming to suggest.

> >   I'm not so keen on removing the getCurrent... but if others
> >   want to I'll go along with it.
>
> I do not think we can manage without the getCurrent... methods can we?

	I believe so. In the reference package I have been fooling around with,
	I put these on the locator class, and it works fine.

	=b.t.

-- 

  * Dr. Brian Thomas 

  * Dept of Astronomy/University of Maryland-College Park 
  * Code 630.1/Goddard Space Flight Center-NASA

  *   fax: (301) 286-1775
  * phone: (301) 286-6128 [GSFC]
           (301) 405-2312 [UMD]