<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi James et all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just a quick note on that. It’s a bit of a guess but I’m suspecting that this might be referring to a Measurement Set (MS), which is a specific data format (and a model) used by CASA (and now ASKAPsoft) to store interferometric visibilities.
So, the data type is then must be “visibilities”. To confuse things further, CASA can store continuum images and spectral-line image-cubes in the same MS format as CASA tables. In my view, it’d be ideal to have two things describing a) the nature of data and
b) its specific format (including version).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Slava<o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">________________________________</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#5DABCE">Dr Slava Kitaeff</span></b><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Australian SKA Regional Centre Program Manager</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">International Centre for Radio Astronomy Research</span></b><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">The University of Western Australia</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Astronomy and Space Science</span></b><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">CSIRO</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Email: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:blue"><a href="mailto:slava.kitaeff@icrar.org"><span style="color:#0563C1">slava.kitaeff@icrar.org</span></a> </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">or <a href="mailto:slava.kitaeff@csiro.au"><span style="color:#0563C1">slava.kitaeff@csiro.au</span></a> </span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Tel.: (+61) (0) 8 6488 7744 (ICRAR) or (+61) (0) 8 6436 8865 (CSIRO)</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Mob.: +61 404 297 414</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><i><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span></i><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Mailing addresses:</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">M468, University of Western Australia, 35 Stirling Highway, Crawley WA 6009, Australia, <b>or</b></span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">CSIRO Astronomy and Space Science, PO Box 1130, Bentley WA 6102, Australia</span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">ICRAR: Discovering the hidden Universe through radio astronomy<b> </b></span><span style="font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif"><a href="http://www.icrar.org"><span style="color:#0563C1">www.icrar.org</span></a><span style="color:black;background:white"> </span></span><a href="http://www.icrar.org/#subscribe"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1">Subscribe
to our eNewsletter</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black;background:white"> </span><a href="http://twitter.com/icrar"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1">ICRAR on Twitter</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black;background:white"> </span><a href="http://www.facebook.com/pages/ICRAR/199692286227"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1">ICRAR
on Facebook</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black"><dal-bounces@ivoa.net> on behalf of "Dempsey, James (IM&T, Black Mountain)" <James.Dempsey@csiro.au><br>
<b>Date: </b>Wednesday, 11 March 2020 at 5:43 pm<br>
<b>To: </b>Markus Demleitner <msdemlei@ari.uni-heidelberg.de>, "dal@ivoa.net" <dal@ivoa.net>, "registry@ivoa.net" <registry@ivoa.net>, "semantics@ivoa.net" <semantics@ivoa.net><br>
<b>Subject: </b>Re: Vocabularising dataproduct_type<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black">Hi Markus,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black">We are dealing with a lot of catalogues as well as images, cubes etc. Currently these have a blank dataproduct_type in the CASDA obscore instance as there wasn't anything
we could use in v1.0. We will probably start using measurements soon as it is better than nothing, but it isn't a term that our community uses. Their expectation is to see catalogue in the type, so I'd be keen to see that as term available for use.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black">Our catalogues are generally source lists produced from the associated image/cube.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;color:black">Cheers,<o:p></o:p></span></p>
</div>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt">James Dempsey<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;background:white">Senior Developer</span><span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;background:white">Information Services Applications</span><span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt">CSIRO Information Management & Technology (IM&T)<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="margin-left:36.0pt;text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="color:black">From:</span></b><span style="color:black"> dal-bounces@ivoa.net <dal-bounces@ivoa.net> on behalf of Markus Demleitner <msdemlei@ari.uni-heidelberg.de><br>
<b>Sent:</b> Wednesday, 11 March 2020 7:48 PM<br>
<b>To:</b> dal@ivoa.net <dal@ivoa.net>; registry@ivoa.net <registry@ivoa.net>; semantics@ivoa.net <semantics@ivoa.net><br>
<b>Subject:</b> Re: Vocabularising dataproduct_type</span> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Hi Sarah,<br>
<br>
On Tue, Mar 10, 2020 at 03:58:09PM +0000, Sarah Weissman wrote:<br>
> * Would too many things be mapped into "Measurement" to be useful<br>
> from a discovery perspective?<br>
<br>
Given my findings yesterday (no active obscore service right now has<br>
measurements rows), I think we shouldn't sweat this measurements<br>
thing too much at this point -- in Registry, this term would only be<br>
used for (SSAP, for now) services *returning* lists of such<br>
measurements (as they would otherwise return spectra), which seems a<br>
long shot.<br>
<br>
Normal discovery of catalogues and similar will of course proceed as<br>
usual.<br>
<br>
However, I largely agree with Laurent:<br>
<br>
On Tue, 10 Mar 2020 17:42:43 +0100, Laurent Michel wrote:<br>
> I would really prefer the list of dataproduct_type to ensur an ascending<br>
> compatibility with Obscore. I believe it is worth to keep as fas as possible a<br>
> consistance betwenn standards. This might help in many cases to map things<br>
<br>
So, even though I think we've found that the actual definition of<br>
measurement is, well, hard, I'm now rather convinced we shouldn't<br>
drop it. On the other hand, when we follow Marco --<br>
<br>
On Tue, 10 Mar 2020 13:53:09 +0100, Molinaro, Marco wrote:<br>
> Il giorno mar 10 mar 2020 alle ore 13:14 Markus Demleitner <<br>
>> A set of derived measurements obtained from a particular original<br>
>> dataset. The prototypical example would be a list of sources<br>
>> extracted from an image.<br>
><br>
> Does it have to be "original dataset" _singular_?<br>
<br>
and Laurent's previous proposal, we'd end up with:<br>
<br>
A set of derived measurements obtained from original datasets or a<br>
catalog of sources.<br>
<br>
I'd say the "obtained from original datasets" in there doesn't really<br>
mean much (what else could the measurements be derived from?), so<br>
reduced it would work out to<br>
<br>
A set of derived measurements or a catalog of sources.<br>
<br>
Which, as Sarah rightly says, is really vague and all-encompassing.<br>
As I said, I'd normally throw out such a term on grounds of it<br>
colliding with too many other terms without really fitting well into<br>
a hierarchy.<br>
<br>
But again, since it's in obscore, we shouldn't drop it. But since<br>
it, to me, seems ill-defined, perhaps we should be frank and just say:<br>
<br>
Generic tabular data not fitting any of the other terms. Because<br>
of its lack of specificity, this term should generally be avoided,<br>
and new, more precise terms should be introduced instead.<br>
<br>
Can people live with that? If we find good use cases for<br>
"measurements" later, we still can get more precise in this<br>
definition as long as we now say "don't use it, really".<br>
<br>
Back to Sarah:<br>
<br>
On Tue, Mar 10, 2020 at 03:58:09PM +0000, Sarah Weissman wrote:<br>
> * Do we need a separate category for "Model"?<br>
<br>
The future Vocabularies 2 standard is designed to make it easy to add<br>
new terms exactly when they're actually needed. So, when you you<br>
have an SSA or Obscore service returning such Models instances -- or<br>
some future use of this vocabulary needs it --, we can include it.<br>
For now, let's see if we can just stick with what Obscore already<br>
has.<br>
<br>
> * Do you expect that more than one label would be applied to a data<br>
> product? For example (naively) could a "spectral image cube" be<br>
> labeled with "spectrum" and "image" and "cube"?<br>
<br>
This depends on where the terms are being used. In obscore, only one<br>
label per row is possible, and I don't think that can be changed in a<br>
backwards-compatible way; we could, however, in some future version<br>
of obscore, introduce a multi-valued "other_dataproduct_types" in the<br>
style of EPN-TAP -- but that's a different discussion.<br>
<br>
In what I'm drafting for SimpleDALRegExt, SSA services can be<br>
annotated with zero or more dataproductType elements (current<br>
internal draft: <a href="http://docs.g-vo.org/SimpleDALRegExt.pdf">http://docs.g-vo.org/SimpleDALRegExt.pdf</a> or on<br>
volute). More on this later on the Registry list.<br>
<br>
Thanks,<br>
<br>
Markus<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>