Fwd: [ivoa-std/SSA] Invalid UCDs : proposal for an erratum to SSA 1.1: meta.curation

Tue Nov 2 10:11:47 CET 2021

Dear Semantics and DAL members,

My apologies for this email, that was stuck in my mail box due to an 
error on recipients on my side .
Sorry for that.
please consider this proposal for the UCD List curation and for a 
revision of usage in SSAP.

Thanks in advance for your comments and feedback.
Mireille
---

Dear Semantics & DAL members,

I have a proposal here for the revision of the UCD terms in the SSA 
specification.
https://ivoa.net/documents/SSA/20120210/ 
<https://ivoa.net/documents/SSA/20120210/>

Currently
/instr.fov /and /meta.curation / are two terms in the spec which:
- are misused  with respect to the meaning of the element they described 
: /instr.fov/
- or are not//compliant with UCD Rules : meta.curation is defined as 
primary term in UCDList1.4 and used also as secondary term .
/
/here I propose to consider /meta.curation/ , a situation which is more 
tricky than/instsr.fov
/
/*meta.curation :

*/Used in SSA appendix table :

*Curation*

**

*Curation Metadata*

**

Curation.Publisher

meta.curation

Dataset publisher

char

Curation.PublisherID

meta.ref.url;meta.curation

URI for VO Publisher

char

Curation.PublisherDID

meta.ref.url;meta.curation

Publisher's ID for the dataset ID

char

Curation.Date

Date curated dataset last modified

char

Curation.Version

meta.version;meta.curation

Publisher's version of the dataset

char

Curation.Rights

Restrictions on data access

char

Curation.Reference

meta.bib.bibcode

URL or Bibcode for documentation

char

Curation.Contact.Name

meta.bib.author;meta.curation

Contact name

char

Curation.Publisher is compliant to UCDList1.4 where the definition gives
P | meta.curation | Identity of man/organization responsible for the data
Curation.PublisherDID deals with identifiers.
Here /meta.ref.url;meta.curation/  is //

  * not compliant w.r.t UCDList1.4 (second position)
  * not fully relevant to the meaning

We could use instead /meta.ref.ivoid /, like proposed in 
/https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-1 
<https://wiki.ivoa.net/twiki/bin/view/IVOA/ObsCore-1_1-Erratum-1>
/

Curation.version associated to /meta.version;meta.curation /seems correct.

But this needs an update for the UCDList to change the flag  to S and 
expand usage as a suffix word .
S | meta.curation | Related to curation of the data

Same for Curation.Contact.Name where we could also use 
/meta.name;meta.curation .

/so if we agree to modify /meta.curation/ to S term ,
we can solve many of the irregular UCD use for curation elements in SSA.

Action for SSA specification :
Curation elements in the protocol can be changed to :

*Curation*

* changes proposed
*

* previous
*

*Curation Metadata*

Curation.Publisher

meta.id;meta.curation

  meta.curation

Dataset publisher

Curation.PublisherID

meta.ref.url;meta.curation

meta.ref.url;meta.curation

URI for VO Publisher

Curation.PublisherDID

meta.ref.ivoid;meta.curation

meta.ref.url;meta.curation

Publisher's ID for the dataset ID

Curation.Date

time.processing;meta.curation

Date curated dataset last modified

Curation.Version

meta.version;meta.curation

Publisher's version of the dataset

Curation.Rights

meta.code.status

Restrictions on data access

Curation.Reference

meta.bib.bibcode

URL or Bibcode for documentation

Curation.Contact.Name

meta.bib.author;meta.curation

Contact name

Curation.Contact.Email

meta.email;meta.curation

meta.ref.url;meta.email

Contact email

/
/Action for UCD update :
- change definition of meta.curation to
S | meta.curation | Related to curation of the data

Action for data providers  :
- previous use of /meta.curation /to replace by /meta.id;meta.curation 
/in existing archives /
/to replace the former primary /meta.curation/

I hope this clarifies the situation.

As a reminder, I emphasize that having /meta.curation/ as Q term
- would be ambiguous for UCD assignation tools,
- would prevent clarify the meaning of many terms combined terms.

Comments and feedback welcome.
Best regards , Mireille

Le 09/09/2021 à 10:16, msdemlei a écrit :
> On Wed, Sep 08, 2021 at 07:18:54AM -0700, Mireille LOUYS wrote:
> > instr.fov represents a geometrical shape on the sky covered by an
> > observing instrument. Table columns should be specified
> > unambiguously to designate what is measured or represented in the
> > column value: phys.angSize;instr.fov , phys.area;instr.fov ,
> > pos.outline;instr.fov
>
> While it may be a nice service to complete UCD assignment in a future
> version of SSAP, I think for the present purpose (remove
> contradictions between different IVOA specs), we should restrict
> ourselves to the UCDs that actually conflict between SSAP and UCD and
> fix those. That's urgent in my book. Anything else may be nice to
> have in order to make SSAP responses more palatable to generic
> clients. But that, I claim, is a rather exotic use case, and anyway
> it doesn't seem particularly urgent.
>
> If you're sure you don't want to adapt UCD to SSAP usage, then it
> seems the only way forward is to write an Erratum for SSAP, and that
> necessarily needs to be restricted to the columns with the invalid
> UCDs.
>
> Who'll write this? Should I?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub 
> <https://github.com/ivoa-std/SSA/issues/1#issuecomment-915867159>, or 
> unsubscribe 
> <https://github.com/notifications/unsubscribe-auth/AICF4GIIZBPZBU3IBC2QYR3UBBUPRANCNFSM5ACKBE4A>.
> Triage notifications on the go with GitHub Mobile for iOS 
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> 
> or Android 
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. 
>
>

-- 
--
Mireille Louys,  MCF (Associate Professor)
Centre de données CDS		IPSEO, 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/semantics/attachments/20211102/a6a3b4be/attachment-0001.html>