<html 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)">
<style><!--
/* Font Definitions */
@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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{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>
</head>
<body lang="en-DK" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="DA" style="mso-fareast-language:EN-US">Thanks Ramona<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DA" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">> </span>
would it help if we assigned URIs to the values in the CVs? That is our eventual plan<span lang="EN-US" style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Yes, longer term this makes sense. I anticipate we’ll probably arrive at SKOS or similar for these kind of vocabularies.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">> …</span>it is less confusing to use the GBIF namespace for URNs<span lang="EN-US" style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thanks. We’ll change to use GBIF namespaces unless someone brings new information and will update the TG report accordingly.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Ramona Walls <rlwalls2008@gmail.com><br>
<b>Date: </b>Thursday, 24 June 2021 at 18.18<br>
<b>To: </b>Tim Robertson <trobertson@gbif.org><br>
<b>Cc: </b>Pier Luigi Buttigieg <pier.buttigieg@awi.de>, "dwc-mixs@lists.tdwg.org" <dwc-mixs@lists.tdwg.org>, Chris Mungall <cjmungall@lbl.gov>, Bill Duncan <wdduncan@gmail.com><br>
<b>Subject: </b>Re: [dwc-mixs] DwC "picklist" extension to MIxS IRIs<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"><br clear="all">
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt">Thank you both for working this out and explaining the details.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I do think it is less confusing to use the GBIF namespace for URNs, rather than append the GSC URIs. Citing the MIxS URI then allows people to find the original term.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Tim, would it help if we assigned URIs to the values in the CVs? That is our eventual plan.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt">Ramona<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">------------------------------------------------------<br>
Ramona L. Walls, Ph.D.<br>
Data Scientist, Ontologies, Semantics, and Metadata, Critical Path Institute<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Assistant Research Professor, Bio5 Institute, University of Arizona<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Part-time artist (<a href="https://www.instagram.com/omnivoresgratitutude/" target="_blank">https://www.instagram.com/omnivoresgratitutude/</a>)<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Jun 22, 2021 at 12:21 PM Tim Robertson <<a href="mailto:trobertson@gbif.org">trobertson@gbif.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks, Pier<br>
<br>
We'll clearly state expectations in the description, and this will be kept as internal as it can be.<br>
<br>
Using the example of the vocabulary of controlled terms for lib_layout[1] currently we have:<br>
<a href="https://w3id.org/gensc/terms/MIXS:0000041/vector" target="_blank">https://w3id.org/gensc/terms/MIXS:0000041/vector</a>
<br>
<br>
This could become something like the following e.g. <br>
<a href="https://rs.gbif.org/vocab/dna/lib_layout/vector" target="_blank">https://rs.gbif.org/vocab/dna/lib_layout/vector</a>
<br>
<br>
Would this be preferable to the GSC folk to avoid confusion, please?<br>
Note that the source from where it is derived will still be cited.<br>
<br>
Thanks,<br>
Tim<br>
<br>
[1] <a href="https://rs.gbif.org/sandbox/vocabulary/mixs/lib_layout.xml" target="_blank">
https://rs.gbif.org/sandbox/vocabulary/mixs/lib_layout.xml</a><br>
<br>
<br>
<br>
<br>
On 22/06/2021, 17.41, "Pier Luigi Buttigieg" <<a href="mailto:pier.buttigieg@awi.de" target="_blank">pier.buttigieg@awi.de</a>> wrote:<br>
<br>
Thanks Tim, this clarifies a great deal.<br>
<br>
Measures to make it clear that the URNs (wherever they appear, e.g. on <br>
documentation pages, lists...) used by legacy systems are not to be <br>
understood as resolvable or under the control/custodianship of the GSC <br>
would help.<br>
<br>
While technically valid, prefixing URNs with HTTP does indeed set a <br>
false expectation - anything that can mitigate that would be appreciated.<br>
<br>
On the GSC and TDWG side however, it would be very interesting to find <br>
out how to do this more sustainably by, e.g., sharing vocabulary files <br>
with all the metadata needed to, e.g., map to ontologies, qualify terms <br>
with comments, include provenance data, etc<br>
<br>
On 22/06/2021 17:18, Tim Robertson wrote:<br>
> Thanks, Pier<br>
><br>
> Just for a bit of background - you're assuming these are IRIs, but the DwC-A work was all designed at a time when URNs were common and expectations of resolvability weren't as high as today.<br>
> The original design was really just to ensure a globally unique URN was used.<br>
><br>
> I think the concerns you raise are valid, and especially with the current intent to achieve resolvability for all the
<a href="http://w3id.org/" target="_blank">w3id.org/.</a>.. terms.<br>
> We do need a URN though, and I understand there isn't an intention to make resolvable terms for these concepts. The
<a href="http://rs.gbif.org" target="_blank">rs.gbif.org</a> namespace has been used for this kind of thing in the past, which might be an alternative option to lower expectations.<br>
><br>
> Thanks,<br>
> Tim<br>
><br>
><br>
><br>
> On 22/06/2021, 16.02, "dwc-mixs on behalf of Pier Luigi Buttigieg" <<a href="mailto:dwc-mixs-bounces@lists.tdwg.org" target="_blank">dwc-mixs-bounces@lists.tdwg.org</a> on behalf of
<a href="mailto:pier.buttigieg@awi.de" target="_blank">pier.buttigieg@awi.de</a>> wrote:<br>
><br>
> Dear TG, Dear Ramona (GSC CIG), Chris, Bill,<br>
><br>
> In our DwC-MIxS mapping activity, we noted a practice to support the IPT<br>
> to generate "picklists" (for drop-down menus etc) by adding extensions<br>
> to IRIs.<br>
><br>
> This was suggested as a means to link the values to keys in<br>
> terminology-focused fields.<br>
><br>
> You can see the link to the "picklists" in the tracker:<br>
> <a href="https://github.com/tdwg/gbwg/tree/main/dwc-mixs/dwc#vocabularies" target="_blank">
https://github.com/tdwg/gbwg/tree/main/dwc-mixs/dwc#vocabularies</a><br>
><br>
> An example is available in [1] and looks like:<br>
> dc:URI='<a href="https://w3id.org/gensc/terms/MIXS:0000005/contigs" target="_blank">https://w3id.org/gensc/terms/MIXS:0000005/contigs</a>'<br>
><br>
> I'm not quite sure about this and would like your input. To me, it seems<br>
> like a very strange way to modify an identifier *issued by another<br>
> standards group* in order to help a tool generate dropdown menu.<br>
><br>
> It essential creates a false impression that there's something<br>
> standardised on the other end of that IRI that may or may not be the case.<br>
><br>
> Best,<br>
><br>
> Pier Luigi<br>
><br>
> [1]<br>
> <a href="https://github.com/tdwg/gbwg/blob/main/dwc-mixs/dwc/vocabulary/contam_screen_input.xml" target="_blank">
https://github.com/tdwg/gbwg/blob/main/dwc-mixs/dwc/vocabulary/contam_screen_input.xml</a><br>
><br>
><br>
> --<br>
> <a href="https://orcid.org/0000-0002-4366-3088" target="_blank">https://orcid.org/0000-0002-4366-3088</a><br>
><br>
> _______________________________________________<br>
> dwc-mixs mailing list<br>
> <a href="mailto:dwc-mixs@lists.tdwg.org" target="_blank">dwc-mixs@lists.tdwg.org</a><br>
> <a href="http://lists.tdwg.org/mailman/listinfo/dwc-mixs" target="_blank">
http://lists.tdwg.org/mailman/listinfo/dwc-mixs</a><br>
><br>
-- <br>
<a href="https://orcid.org/0000-0002-4366-3088" target="_blank">https://orcid.org/0000-0002-4366-3088</a><br>
<br>
<o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>