<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi all , <br>
<br>
Thanks Markus for writing this ObsCore erratum 4 about data_rights
defined at the level of a data product. <br>
<br>
I think it fixes the issue. <br>
<br>
The data rights was thought to be a property of the data set itself,
so I don't see why this should <br>
disappear from the Obscore data model.<br>
It is an optional parameter, but may be used when a data base is
reorganised , in order to distinguish for instance <br>
between a public thumbnail image (or 1D profile) and the private
image (spectrum) data set .<br>
In my mind , this property belongs to the data file, and the ObsTAP
service may or may not use it in the discovery.<br>
However, maintenance and update of a service may use it. <br>
<br>
Other data rights in the landscape: <br>
<ul>
<li><i>DatasetMetadata WD</i> uses RightsType <br>
PUBLIC public unrestricted, public access is allowed, without
authentication.<br>
SECURE secure authenticated, public access is allowed.<br>
PROPRIETARY proprietary only proprietary access is allowed with
authentication.values <br>
</li>
</ul>
for the item Curation.rights : Curation.rights 0..1
Level of access granted meta.code<br>
<ul>
<li><i>Spectrum DM 1.2</i> has another list of enumerated values
for data rights which is :<br>
<i>public , proprietary, mixed </i>as defined in Table 1,
p.17 of the proposed recommendation <br>
<a
href="https://ivoa.net/documents/SpectrumDM/20230907/PR-SpectrumDM-1.2-20230907.pdf"
class="moz-txt-link-freetext">https://ivoa.net/documents/SpectrumDM/20230907/PR-SpectrumDM-1.2-20230907.pdf</a><br>
</li>
</ul>
it is worth harmonizing the definitions between these specifications
, so may be re-use the citation proposed in the Obscore Erratum 4? <br>
<a
href="https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-4"
rel="noreferrer" target="_blank" class="moz-txt-link-freetext">https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-4</a><br>
<br>
How many SSA services are there currently in the VO using
Curation.Rights='mixed'? <br>
<br>
best wishes, Mireille.<br>
<br>
<br>
<div class="moz-cite-prefix">Le 10/10/2023 à 19:35, Patrick Dowler a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAFK8nrrpcJH9yP+9gGBGWg9yBkeMDhWnrm6g=1c-NHuMS9p_zA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">CAOM includes
a data release date value that we include in our ivoa.ObsCore
view; beyond that we </div>
<div class="gmail_default" style="font-size:small">use GMS group
identifiers to indicate who is allowed to access data when
data release date is not in <br>
</div>
<div class="gmail_default" style="font-size:small">the past
(null or future means proprietary, past means "public"). After
many years of dealing with </div>
<div class="gmail_default" style="font-size:small">proprietary
telescope data, none of the simpler seeming middle ground is
worth the effort so I know </div>
<div class="gmail_default" style="font-size:small">we won't try
to do anything with data_rights.<br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">other related
tidbit:<br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">DataLink-1.1
includes 2 optional fields related to telling clients about
auth requirements; that's driven mainly</div>
<div class="gmail_default" style="font-size:small">by clients
wanting to decide "if I use this link, will it work or will I
get rejected?". That seems to conceptually</div>
<div class="gmail_default" style="font-size:small">overlap with
data_rights but happens down at the resource (file) level...
It's often the case that rights differ at</div>
<div class="gmail_default" style="font-size:small">this level
(e.g. public thumbnail or preview but proprietary data) so
such an indicator at the discovery level</div>
<div class="gmail_default" style="font-size:small">(ObsCore or
CAOM) isn't very useful in practice.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">Otherwise:
the erratum looks good to fix the reference issue.<br>
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div>--<br>
</div>
<div>Patrick Dowler<br>
</div>
Canadian Astronomy Data Centre<br>
</div>
Victoria, BC, Canada<br>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 10 Oct 2023 at 08:53,
Dubois-Felsmann, Gregory P. <<a
href="mailto:gpdf@ipac.caltech.edu" moz-do-not-send="true"
class="moz-txt-link-freetext">gpdf@ipac.caltech.edu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">For
the record, this definitely addresses my original concerns.<br>
<br>
Gregory<br>
<br>
________________________________________<br>
From: dm <<a href="mailto:dm-bounces@ivoa.net"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">dm-bounces@ivoa.net</a>> on
behalf of Markus Demleitner <<a
href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">msdemlei@ari.uni-heidelberg.de</a>><br>
Sent: Tuesday, October 10, 2023 12:08 AM<br>
To: <a href="mailto:dm@ivoa.net" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">dm@ivoa.net</a><br>
Subject: Re: ObsCore's data_rights and VODataService - broken
reference<br>
<br>
Dear DM,<br>
<br>
On Fri, Oct 06, 2023 at 06:36:58PM +0000, Dubois-Felsmann,
Gregory P. wrote:<br>
> Pinning the VODataService version to 1.1 in an erratum
sounds reasonable.<br>
<br>
Since nobody else commented, I took that as an encouragement
to clean<br>
up the mess I've caused. The result is Obscore Erratum 4,<br>
<br>
<a
href="https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-4"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-4</a><br>
<br>
Would that be all right with the WG? If so, would you forward
it to<br>
the TCG for review?<br>
<br>
Thanks,<br>
<br>
Markus<br>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Associate Professor)
Centre de données CDS Images, Laboratoire ICube &
Observatoire de Strasbourg Telecom Physique Strasbourg
11 rue de l'Université 300, Bd Sebastien Brandt CS 10413
F- 67000-STRASBOURG F-67412 ILLKIRCH Cedex
Tel: +33 3 68 85 24 34</pre>
</body>
</html>