<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<font face="Times New Roman, Times, serif">Hi Mark, hi all, <br>
<br>
Thanks for the comment .<br>
<br>
We had a recent discussion here Strasbourg , and noticed that <br>
the proposition I wrote in <a class="moz-txt-link-freetext"
href="http://mail.ivoa.net/pipermail/dm/2016-September/005420.html">http://mail.ivoa.net/pipermail/dm/2016-September/005420.html</a>,
was actually an ID for a table and not for the model itself. <br>
<br>
As I mentionned in the referenced mail above, a dedicated TAP
service may serve extra tables together with the ObsTAP
ivoa.ObsCore table.<br>
I feel uneasy to define the scope for an ObsTAP service and I
guess we will have to discuss between several options among which:<br>
a- an ObsTAP service follows the TAP specification and contains at
least the ivoa.Obscore table and possibly more tables defined in
the TAP_SCHEMA .<br>
it has no version by itself , as all tables used have their own
version specified in their identifier.<br>
in this way , ObsTAP is seen as a container with a referenced
model and additionnal tables, not necessarily standardized. <br>
b- an ObsTAP service contains only the ivoa.ObsCore table and its
version is the one of the ObsCore DM. <br>
<br>
I guess it is interesting to open the possibility for data
providers to offer ObsCore++ services , and so warrant a core
level of interoperability for the ObsCore metadata. <br>
However the consistency between the added tables and Obscore might
be "swept under the carpet". ( not made explicit) <br>
<br>
</font>
<ul>
<li><font face="Times New Roman, Times, serif">in case a) the
TAPregext should have at least one declaration specifying the
table reference like the one proposed last june : </font></li>
</ul>
<font face="Times New Roman, Times, serif"><i><dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore/v1.0">ivo://ivoa.net/std/ObsCore/v1.0</a>">ObsCore-1.0</dataModel>
for Obscore 1.0<br>
or </i><br>
<i><dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore#core-1.1">ivo://ivoa.net/std/ObsCore#core-1.1</a>">ObsCore-1.1</dataModel>
for Obscore 1.1<br>
</i><br>
</font>
<ul>
<li><font face="Times New Roman, Times, serif">in case b) we might
have several datamodel references for the same TAP service </font></li>
</ul>
<font face="Times New Roman, Times, serif">for instance for version
1.1 if we want to add a Provenance table to the ObsCore core
table, we would have: <br>
<i><dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore#core-1.1">ivo://ivoa.net/std/ObsCore#core-1.1</a>">ObsCore-1.1</dataModel><br>
and <dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore#core-1.1">ivo://ivoa.net/std/Prov#core-1.0</a>">Prov-1.0</dataModel><br>
<br>
or for a spectrum combined with annotated emission lines<br>
</i><br>
<i><dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore#core-1.1">ivo://ivoa.net/std/ObsCore#core-1.1</a>">ObsCore-1.1</dataModel></i><br>
<i><dataModel ivo-id="<a
href="ivo://ivoa.net/std/ObsCore#core-1.1">ivo://ivoa.net/std/SSLDM#1.0</a>">ObsCore-1.1</dataModel></i>
<br>
Behind this I guess there is such a question : <br>
At which granularity level does the interoperability take place ?
<br>
at the level of a model ? or at the level of a table definition ?<br>
<br>
Your comments welcome. <br>
Cheers, Mireille.</font><br>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 12/09/2016 à 13:58, Mark Taylor a
écrit :<br>
</div>
<blockquote
cite="mid:alpine.LRH.2.20.1609121253080.2776@andromeda.star.bris.ac.uk"
type="cite">
<pre wrap="">Mireille,
this version PR-ObsCore-v1.1-20160909 specifies in section 5 the
ObsCore 1.1 ivoid:
ivo://ivoa.net/std/ObsCore#1.1
That is different from what was in the previous draft I saw
(PR-ObsCore-v1.1-20160709) and what I recall being agreed in
email discussions, e.g.
<a class="moz-txt-link-freetext" href="http://mail.ivoa.net/pipermail/dm/2016-September/005420.html">http://mail.ivoa.net/pipermail/dm/2016-September/005420.html</a>,
which specified:
ivo://ivoa.net/std/ObsCore#core-1.1
Can you confirm that the current draft is really as intended?
Thanks.
Mark
On Fri, 9 Sep 2016, Mireille Louys wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear DMers,
Please find here a revised version of the Obscore 1.1 specification .
After discussion among authors about the addition of analysis results like
source lists/catalogs, and calibration levels values,
here is the proposal.
More details next week about the pros and cons.
Thanks for your comments,
Mireille Louys
</pre>
</blockquote>
<pre wrap="">--
Mark Taylor Astronomical Programmer Physics, Bristol University, UK
<a class="moz-txt-link-abbreviated" href="mailto:m.b.taylor@bris.ac.uk">m.b.taylor@bris.ac.uk</a> +44-117-9288776 <a class="moz-txt-link-freetext" href="http://www.star.bris.ac.uk/%7Embt/">http://www.star.bris.ac.uk/~mbt/</a>
</pre>
</blockquote>
<br>
</body>
</html>