<div dir="ltr"><div>Markus,</div><div><br></div><div>I'll respond to a couple points here.. other items will need more thought/consideration.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 15, 2020 at 7:33 AM Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a>> wrote:<br></div><div class="gmail_attr"><snip></div><div class="gmail_attr"><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">> On Mon, Sep 7, 2020 at 10:54 AM Markus Demleitner <<br>
> <a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a>> wrote:<br>
> The difference is basically:<br>
> * with just GenericMeasure your data product will only be making the<br>
> statement<br>
> "This TABLE has COLUMNS"<br>
> * with the property-based Measures, you are describing Entities<br>
> "This Cube has Position, Time, etc...<br>
<br>
As you know I'm always trying to limit the number of ways we have in<br>
the VO to do roughly the same thing, so: How is this different from<br>
attaching a UCD to the GenericMeasure?<br></blockquote><div><br></div><div>IMO: you are mixing "model" and "serialization" here.</div><div>I would rephrase your sentence as:</div><div> "A standard serialization of the Position, Time, etc model objects in VOTable COULD be to attach an appropriate UCD to the <GROUP> element."</div><div>But, that does NOT mean that UCD should be a model element... it is a means of representing the concept which may work well for VOTables, but not necessarily for other formats.</div><div><br></div><div> </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">> One of the 'threads' often used in the wish-list for these models is to<br>
> 'easily identify and plot the positions in a file, with<br>
> appropriate/normalized Frame specs'.<br>
<br>
But shouldn't such applications simply look for Coordinates instances<br>
rather than going as deep as Measurements?<br></blockquote><div><br></div><div>Coordinates is deeper than Measurements.</div><div><br></div><div>Mark</div><div><br></div></div></div>