<div dir="ltr">Thanks Nancy we can take a look at our next meeting!<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 3, 2022 at 9:33 PM Nancy Wiegand <<a href="mailto:wiegand@cs.wisc.edu">wiegand@cs.wisc.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">
<div><p style="text-align:center"><font color="red"><strong>External Email</strong><br></font></p>
<p>I used an old address, I guess.<br>
</p>
<div><br>
<br>
-------- Forwarded Message --------
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Subject:
</th>
<td>I added a section to the ESIP Semantic Harmonization
experience paper</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Date: </th>
<td>Tue, 3 May 2022 14:30:19 -0500</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">From: </th>
<td>Nancy Wiegand <a href="mailto:wiegand@cs.wisc.edu" target="_blank"><wiegand@cs.wisc.edu></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">To: </th>
<td>Gary Berg-Cross <a href="mailto:gbergcross@gmail.com" target="_blank"><gbergcross@gmail.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">CC: </th>
<td>Ruth Duerr <a href="mailto:ruth.duerr3@gmail.com" target="_blank"><ruth.duerr3@gmail.com></a>, Kai Blumberg
<a href="mailto:kblumber@mpi-bremen.de" target="_blank"><kblumber@mpi-bremen.de></a>, Pier Buttigieg
<a href="mailto:pier.buttigieg@awi.de" target="_blank"><pier.buttigieg@awi.de></a>, Kate Rose
<a href="mailto:Kate.rose@noaa.gov" target="_blank"><Kate.rose@noaa.gov></a>, Pier Buttigieg
<a href="mailto:pbuttigi@mpi-bremen.de" target="_blank"><pbuttigi@mpi-bremen.de></a>, Nancy Wiegand
<a href="mailto:wiegand@cs.wisc.edu" target="_blank"><wiegand@cs.wisc.edu></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<p>To describe our latest matching process, I added a section. <span style="font-weight:normal"><span style="font-size:14pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"></span></span><b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-4c2efa9f-7fff-1272-206b-972a2cab811c"><span style="font-size:14pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">You can use it or not, or edit, whatever.
</span></b></p>
<p><b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-4c2efa9f-7fff-1272-206b-972a2cab811c"><span style="font-size:14pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Aligning ENVO Terms with SWEET</span></b><b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-60410bf1-7fff-b88f-183a-b703de70a5f4"><br>
</b></p>
<p><b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-60410bf1-7fff-b88f-183a-b703de70a5f4"><br>
</b></p>
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-60410bf1-7fff-b88f-183a-b703de70a5f4"><span style="font-size:11pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">As part of our harmonization project, after adding cryo terms to ENVO, we then mapped those ENVO terms to SWEET for the purpose of aligning the two ontologies. To do this, we first populated a spreadsheet with our newly entered ENVO terms alongside potential matching terms in SWEET and, for each term, using a human curated approach versus machine learning or automated string matching, determined a potential relationship expressed using SKOS mappings. As a group endeavor (e.g., 4-5 people), we looked up definitions using BioPortal (<a href="https://bioportal.bioontology.org/search" target="_blank">https://bioportal.bioontology.org/search</a>) for SWEET and a lookup service for ENVO (e.g., <a href="https://www.ebi.ac.uk/ols/ontologies/envo" target="_blank">https://www.ebi.ac.uk/ols/ontologies/envo</a>), and had a discussion, also noting where the term occurred in each class hierarchy. </span></b></p>
<b style="font-weight:normal" id="gmail-m_4897610828275873795docs-internal-guid-60410bf1-7fff-b88f-183a-b703de70a5f4"> <br>
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">SWEET, however, does not have definitions for many of its terms. So, even if the ENVO and SWEET terms matched string-wise, we refrained from calling it an 'exact match'. An example is the ENVO term 'ice sheet' and SWEET's 'IceSheet' for which we chose 'close match' (skos:closeMatch) because of a lack of a SWEET definition. We noted this by recording a comment that ice sheet is a candidate for an exact match if SWEET were to add ENVO's definition to SWEET's term at some future time. Our intent now is not to presume exact definitions without an existing definition in SWEET.</span></p>
<br>
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">As mentioned, we also looked at class hierarchies to determine closeness of match. It was found that some very similar terms, even nearly exact strings, had a different basic upper parent class in each ontology, such as 'freezing rainfall' in ENVO and 'FreezingRain' in SWEET. We recorded this match as close instead of exact and commented that ENVO classifies the concept as a type of 'process', but SWEET has it as a type of atmospheric precipitation which is under 'phenomena'. </span></p>
<br>
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:"Times New Roman";color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">An example of a related match (skos:relatedMatch) is ENVO's 'snow layer' and SWEET's 'SnowCover'. Further, SWEET has two instances of SnowCover, one under 'phenHydro' (hydrospheric phenomenon) and the other under 'propSpaceThickness' (a thickness). To handle this, we made two copies of ENVO's 'snow layer' and mapped each as related to SWEET's terms. An example of a broader match (skos:broadMatch) is ENVO's 'planetary cryosphere' mapped to SWEET's 'cryosphere'.</span></p>
</b><br>
</div>
</div>
</blockquote></div>