<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace">Hi Markus, hi Registry,</div><div class="gmail_default" style="font-family:monospace">(CC'ing TCG to alert a Std's discussion topic)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mer 24 ago 2022 alle ore 13:37 Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Registry community,<br>
<br>
Now that we have a proper vocabulary reflecting the UAT in the VO, we<br>
can finally fix VOResource to actually explain what "use the UAT in<br>
subject" means.<br>
<br>
This is not super-urgent; we could thus go for VOResource 1.2 with<br>
this. However, I don't see a sizable number of other changes that<br>
would warrant a new document version. I would hence suggest that an<br>
erratum should do it, too.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:monospace">I have a feeling that using an erratum for </div><div class="gmail_default" style="font-family:monospace">the update proposed below would be stretching </div><div class="gmail_default" style="font-family:monospace">the scope of errata.</div><div class="gmail_default" style="font-family:monospace">(BTW: I agree on the proposed change to the </div><div class="gmail_default" style="font-family:monospace">specification in full -- erratum content --)</div></div><div><br></div><div><div class="gmail_default" style="font-family:monospace">I would rather see a different approach to </div><div class="gmail_default" style="font-family:monospace">the review process for cases like this one.</div><div class="gmail_default" style="font-family:monospace"></div><div class="gmail_default" style="font-family:monospace">My view/proposed approach:</div><div class="gmail_default" style="font-family:monospace">- the update is limited to a few sections/parts </div><div class="gmail_default" style="font-family:monospace">of the specification</div><div class="gmail_default" style="font-family:monospace">- a WD and then a PR is set up with the changes</div><div class="gmail_default" style="font-family:monospace">- the RFC states clearly at top that _only_</div><div class="gmail_default" style="font-family:monospace">those sections need to be reviewed</div><div class="gmail_default" style="font-family:monospace">- comments outside this scope are noted down but </div><div class="gmail_default" style="font-family:monospace">dismissed </div><br></div><div><div class="gmail_default" style="font-family:monospace">Doing so, supposing a quick WD period in the WG </div><div class="gmail_default" style="font-family:monospace">applies (and I don't see why this shouldn't happen </div><div class="gmail_default" style="font-family:monospace">in this case), the 6-weeks period for RFC & vote</div><div class="gmail_default" style="font-family:monospace">should really be enough (just look at the proposed </div><div class="gmail_default" style="font-family:monospace">changes at bottom to have an idea on this).</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Cheers</div><div class="gmail_default" style="font-family:monospace"> Marco</div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I've just written a proposal for one -- see below. Feel free to<br>
comment and suggest improvements (or to protest if you see major<br>
flaws or insist on VOResouce 1.2). If I hear nothing, I'll move the<br>
thing on to the TCG in two weeks.<br>
<br>
✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂<br>
<br>
---++ Rationale<br>
<br>
VOResource 1.1 says in the documentation of the subject element:<br>
<br>
Terms for Subject should be drawn from the Unified Astronomy Thesaurus<br>
(<a href="http://astrothesaurus.org" rel="noreferrer" target="_blank">http://astrothesaurus.org</a>).<br>
<br>
This prescription is not suffient in practice; for many reasons, we<br>
cannot really use the UAT concept URIs (for instance,<br>
<a href="http://astrothesaurus.org/uat/11" rel="noreferrer" target="_blank">http://astrothesaurus.org/uat/11</a> for "The relative amount of a given<br>
chemical element with respect to other elements") in VOResource. The<br>
label (in the example, "Abundance ratios") is not necessarily stable and<br>
suffers from case and potentially punctuation issues.<br>
<br>
To have a solid foundation for UAT use in VOResource, a specific scheme<br>
has recently been endorsed in the VO, "Adopting the UAT as an IVOA<br>
vocabulary", <a href="https://ivoa.net/documents/uat-as-upstream/" rel="noreferrer" target="_blank">https://ivoa.net/documents/uat-as-upstream/</a>. This is what<br>
should now be used in VOResource, and hence the document should contain<br>
a pointer to the UAT adoption note. This erratum introduces these<br>
pointers and updates an example to the modern practice.<br>
<br>
---++ Erratum content<br>
<br>
In the example at the beginning of section 2 VOResource 1.1, replace:<br>
<br>
<subject>radio astronomy</subject> <br>
<subject>data repositories</subject> <br>
<subject>digital libraries </subject> <br>
<subject>grid-based processing</subject> <br>
<br>
with:<br>
<br>
<subject>radio-astronomy</subject> <br>
<subject>astronomy-software</subject> <br>
<subject>astronomy-web-services</subject> <br>
<subject>search-for-extraterrestrial-intelligence</subject> <br>
<br>
In section 2.2.3 "Language and Transliteration", replace "description,<br>
title, subject", mentioned as examples of elements containing natural<br>
language, with "description or title").<br>
<br>
In section 3.1.3 "General Content Metadata", replace the Comment on<br>
"Element subject" with:<br>
<br>
The content of subject SHOULD be a fragment identifier of the URI of a<br>
concept in the IVOA UAT (<a href="https://www.ivoa.net/rdf/uat/" rel="noreferrer" target="_blank">https://www.ivoa.net/rdf/uat/</a>), that is, a<br>
string like "virtual-observatories". For further details, see the<br>
IVOA endorsed note on Adopting the UAT for the VO,<br>
<a href="https://ivoa.net/documents/uat-as-upstream/" rel="noreferrer" target="_blank">https://ivoa.net/documents/uat-as-upstream/</a>.<br>
<br>
In the XML schema delivered with VOResource 1.1, replace the content of<br>
second xs:documentation element within the xs:element definition of<br>
subject (line 694) with the comment text replaced into section 3.1.3.<br>
<br>
---++ Impact Assessment<br>
<br>
At the moment subject simply is not machine-readable and hence its<br>
content is treated as plain text. TOPCAT, for instance, translates<br>
subject constraints into <br>
<br>
LOWER(res_subject) like '%keyword%'.<br>
<br>
These will obviously keep working as before (except if a data provider<br>
actually had introduced upstream UAT URIs; none has, so far).<br>
<br>
The syntax chosen in the UAT note – words separated by hyphens – also<br>
makes queries using ivo_haswords work as before. During the review<br>
phase of this erratum, the TAP service at <a href="http://dc.g-vo.org/tap" rel="noreferrer" target="_blank">http://dc.g-vo.org/tap</a> carries<br>
table rr.uat_concept that reflects how rr.res_subject will look like<br>
once the UAT migration is finished. To illustrate the effects on<br>
queries using haswords, try:<br>
<br>
select distinct uat_concept from rr.subject_uat<br>
where 1=ivo_hasword(uat_concept, 'radio')<br>
<br>
there.<br>
<br>
Hence, we do not expect noticable negative impact. On the other hand, a<br>
migration to the scheme forseen here will enable many useful<br>
applications, starting from reliable keyword matching to semantics-based<br>
query expansion to subject mapping for interdisciplinary metadata<br>
repositories (cf.<br>
<a href="https://blog.g-vo.org/semantics-cross-discipline-discovery-and-down-to-earth-code.html" rel="noreferrer" target="_blank">https://blog.g-vo.org/semantics-cross-discipline-discovery-and-down-to-earth-code.html</a>).<br>
<br>
✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂<br>
<br>
-- Markus<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div><font face="monospace">Marco Molinaro</font></div><div><font face="monospace">INAF - Istituto Nazionale di AstroFisica</font></div><div><font face="monospace">Osservatorio Astronomico di Trieste</font></div><div><font face="monospace">email <a href="mailto:marco.molinaro@inaf.it" target="_blank">marco.molinaro@inaf.it</a></font></div><div><span style="font-family:monospace">tel. [+39] 333 33 20 564 [also Telegram]</span><br></div></div></div></div></div></div></div>