<div dir="ltr"><div dir="ltr"><div>Markus,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 29, 2020 at 7:58 AM Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br>
Let me ask back here (because I find that consequence rather<br>
unwelcome): Say we have the following dependency graph on the DMs:<br>
<br></blockquote><font face="monospace"><div class="gmail_quote"><font face="monospace"> |- Spectral</font></div><div class="gmail_quote"><font face="monospace"> |- TimeSeries</font></div>coord - meas - dataset - cube<br> `---- phot ----'</font><div><span style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium"><br></span></div>I'm wondering how that works in the higher level products...</div><div class="gmail_quote">I've added TimeSeries and Spectral to your hierarchy chart.</div><div class="gmail_quote"> * Having given this no thought.. If these are isolated models, I'd expect that Spectral and TimeSeries could not be expressed as a simple extension of Cube (as the current prototype model is).</div><div class="gmail_quote"><br></div><div class="gmail_quote">If I'm a provider of Spectra, Photometry filters, TimeSeries, etc..</div><div class="gmail_quote"> 1) How do I know that I should provide annotations for the 'data' as Measurements and Coordinates?</div><div class="gmail_quote"> 2) From that perspective wouldn't I expect that annotating as a TimeSeries should be all I need to do?</div><div class="gmail_quote"> o If I neglect/fail to provide them, it is a valid TimeSeries, but one with no Measurements.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Mark</div><div class="gmail_quote"><div> </div></div></div></div>