[Observation] relation to Dataset

[CresitelloDittmar, Mark]

Arnold,

I agree that we need to distinguish between Observation and Dataset, even
for the ImageDM project.
That is the goal of this thread..

I will be working some new UML diagrams for the 'Desired' model.. based no
these threads, which I hope will help in this matter.

Mark


On Fri, Nov 22, 2013 at 10:04 AM, Arnold Rots <arots at cfa.harvard.edu> wrote:

> I strongly object to this statement:
>
>
> "the data product may be the result of combining data from multiple
> primary (physical) observations.  In this case the resulting data product
> is a new processed "observation" to which a new unique observation
> identifier should be assigned."
>
> We really need to distinguish clearly between Datasets and Observations.
> An Observation represents an operation that is characterized by a
> configuration
> - instrument characteristics, coordinate volume and properties,
> calibration, etc.
> A Dataset is a container of bytes that may have resulted from an
> Observation
> (the byte stream that came out of the telescope or various direct
> processing
> products of it), a simulation, or the processing and analysis of (possibly
> a subset)
> of one or more parent Datasets.
> Each Dataset also carries metadata detailing coordinate characteristics,
> the nature
> of the Dataset and its components, and its provenance regarding its
> parents.
>
> Blurring the line between Observations and Datasets and carelessly forcing
> one
> to assume the characteristics of the other is going to get us into major
> trouble.
>
> Cheers,
>
>   - Arnold
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dm/attachments/20131122/9cbbad63/attachment.html>