Revised ImageDM-ObsCore architecture

CresitelloDittmar, Mark mdittmar at cfa.harvard.edu
Tue Nov 12 20:45:22 PST 2013


Doug..


On Tue, Nov 12, 2013 at 5:29 PM, Douglas Tody <dtody at nrao.edu> wrote:

> On Tue, 12 Nov 2013, CresitelloDittmar, Mark wrote:
>
>
>
>> ObservationDM Package:
>>  Is what is needed by Image/Spectral.  That is in pretty close agreement
>> with Spectral..
>>  there are name differences for things like dataProductType.
>>  Note:
>>   - got rid of "Dataset" class.. the ObservationDataset IS a dataset.
>>   - this does NOT include the Provenance objects.. they are not in
>> Spectral.
>>     They could be.. (since 0 is allowed).
>>
>
> I need to review your new figures but I think the obvious class names
> are Observation, Characterisation, Image, etc.


In re-reading the ObsCore model, it seemed clear that the content was
focused
on the 'Core' components of a larger (and undefined) "Observation" model.
I probably should not have renamed that model's Observation Class, but
it seems clear that it is just the core components.

"Observation" is probably synonymous with "ObservationDataset" in my
diagram,
but I am wanting to emphasize that the intent is that this object IS a
dataset.


>
>  ImageDM package
>>  - adds a Provenance container (from Doug's diagram).  Note that ObsCore
>> does not have
>>    a Provenance class, but associates ObsConfig and Proposal directly.
>>  - adds CoodSys object.
>>
>
> I don't understand this - ObsCore does include Provenance.  See for
> example Figure 2, and Table 5 on pg 37.
>
> Right, Figure 2 shows the Observation class associating with 2 classes
in the Provenance package.  So there is no "Provenance" class in the
ObsCore diagram.
Table 5 shows UTypes which include a Provenance node.. thus implying a
class which
is not in the diagram.

In this case, I would prefer a Provenance container.

>The current Image/Spectral DataID, Target,Curation elements are somewhat
>bigger than what Observation defines, but not that much.  Note the more
>complete version of the model is in Appendix B.  DataID for example,
>defines six elements but only two are in the mandatory "core".  Spectral
>and Image do add a couple more.
Yes.. appendix B shows 6 attributes in DataID, which I include in the
ObsCore Package.
Spectral has 14 attributes in DataID, the 6 from ObsCore, plus 8 more...
which I
show under ObservationDM

I agree that these are generic objects and not particular to
Spectral/Image, which
is why they are in the separate package.  This is also why I moved the
"FluxSI" type
stuff to the BaseSPS extension.. they seem Spectral Specific.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dm/attachments/20131112/a810cb6d/attachment.html>


More information about the dm mailing list