<html xmlns:v="urn:schemas-microsoft-com:vml" 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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:"Andale Mono";
panose-1:2 11 5 9 0 0 0 0 0 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Monaco;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Andale Mono";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Andale Mono"">With the disclaimer that I too have become embroiled in (and occasionally instigated) measurement convention dust-ups around whether the granularity is too fine | coarse:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Andale Mono""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Andale Mono"">Maybe it is time to admit that we will *<b>never</b>* achieve universal or maybe even widespread agreement on which convention (CF, CSDMS, GCMD / UMM-Var, Airborne Atmospheric Chemistry, SWEET, etc.)
properly addresses what level of granularity. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Andale Mono""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Andale Mono"">Maybe we should devote our energy instead to describing and even quantifying the level of granularity of the different conventions and working out how to provide scalable SKOS-ish bridges among them.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Monaco;color:black">—<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Monaco;color:black">Christopher Lynnes NASA/GSFC 301-614-5185<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Monaco;color:black">“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” A. de St. Exupery</span><span style="font-family:"Andale Mono""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Andale Mono""><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal">On 1/15/20, 05:12, "esip-semanticweb on behalf of Siri Jodha Khalsa via esip-semanticweb" <<a href="mailto:esip-semanticweb-bounces@lists.esipfed.org">esip-semanticweb-bounces@lists.esipfed.org</a> on behalf of
<a href="mailto:esip-semanticweb@lists.esipfed.org">esip-semanticweb@lists.esipfed.org</a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>All,<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Last summer ESDIS conducted a <a href="https://rms.earthdata.nasa.gov/review.req#/r:REV-492">
review</a> of a proposed evolution of ESDIS's Unified Metadata Model - Variables (UMM-Var). From the Introduction (since some of you may not have access to the JAMA review system,
<b>emphasis</b> mine):<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The UMM Variables Model (UMM-Var) has a field called 'MeasurementName', which allows metadata curators to provide
<b>community-sourced names</b> to further describe variable data, and hence the measurements which these data variables describe. The UMM-Var encourages tagging of variables with standardized Measurement Names that can be surfaced in NASA's Earthdata Search
when users conduct an End-to-End Services search and discovery workflow, and can help cluster similar variables, even when their native names are quite dissimilar. The UMM-Var approach to Measurement Names is to tag (or associate) variables with standard Measurements
from <b>community-reviewed sources</b> that help identify the most important characteristics of the variable, i.e., the object of the measurement, and the quantity being measured. The mechanism with which we do this is the subject of this review.<o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The purpose of this review is to determine if the recommended approach and revised field structure for Measurement Names is appropriate for all stakeholders who will be adding and populating
Measurement Names in UMM-Var records. The goal is to have a high-quality, normalized, and structured set of Measurement Names that are
<b>semantically-interoperable</b>. <o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">An additional purpose of this review is to ensure that appropriate community sources of Measurement Names are being captured. We are starting out with a "seed" list here. There may be
additional sources of Measurement Names that could be considered and NASA should be aware of these when populating UMM-Var records in the Common Metadata Repository (CMR).<o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="background:white;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-style:
initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Note: This review is not just about the Measurement Names, but the approach for making them controlled and the revised field structure in the UMM-Var. These go hand-in-hand. We also want
to make sure we are looking at the right sources for the Measurement Names. We are not making up new Measurement Names, just deriving them from well-vetted community sources. The list in the proposal is the preliminary list to "seed" the Keyword Management
System, and that will expand over time as we add additional Measurement Names<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal">The review generated a lot of discussion about GCMD vs CSMDS, SWEET, CF, ENVO, etc., and how to manage community-contributed terms and vocabularies. I have added the manager of that review, Simon Cantrell, to this thread to hopefully 1)
solicit his input on the current discussion, 2) explain the status of UMM-Var and 3) also explain why the GCMD Measurement Names seem to entirely ignore where UMM-Var appeared to be headed, i.e. 'MeasurementName' is composed of MeasurementIdentifiers, MeasurementObject,
MeasurementQuantity, MeasurementContextMedium and MeasurementUnits, each of which is a controlled list.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Cheers,<o:p></o:p></p>
<p>SiriJodha<o:p></o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 1/14/20 4:46 PM, Stevens, Tyler B. (GSFC-423.0)[Stinger Ghaffarian Technologies] wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">Siri-Jodha,</span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
<div>
<pre><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p> </o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">Regarding the measurement keywords, the EOSDIS data centers needed a more fine-grained list of specific measurements (e.g.atmosphere_absorption_optical_thickness_due_to_black_carbon_ambient_aerosol_at_532nm) than the science keywords offered. </span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">The recommendation for this was put forward in an ESO review, approved by ESDIS, and there is a preliminary list of 100 measurements. We plan to put forward additional measurement keywords in an upcoming keyword release, and we can add interested folks </span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">here in that review. The measurement keywords specifically support the NASA UMM Variables Model (UMM-Var) evolution which has a field called 'MeasurementName' that allows metadata curators to provide community sourced names to further describe variable </span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">data. </span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130"><o:p> </o:p></span></pre>
</div>
<div>
<pre><span style="font-family:"Calibri",sans-serif;color:#323130">We are also planning to talk to the EOSDIS data centers and others about their data format keywords in preparation for an ESO review. The end-user goal is to allow users to search for data specifically by its format and to address the following use case:</span><span style="color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><i><span style="font-family:"Calibri",sans-serif;color:#323130">As a user, I want to search for collections with granules that have a specific data format (e.g., NetCDF, HDF5, etc). </span></i><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p> </o:p></span></pre>
</div>
<div>
<pre><span style="font-family:"Calibri",sans-serif;color:#323130">The initially discussion here has been very helpful. </span><span style="color:#323130"><o:p></o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130"><o:p> </o:p></span></pre>
</div>
<div>
<pre><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#323130">Thanks,</span><span style="font-family:"Calibri",sans-serif;color:#323130"><o:p></o:p></span></pre>
</div>
</div>
<div id="Signature">
<div>
<div>
<p><span style="font-size:12.0pt">Tyler Stevens</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt">KBR | Senior Discipline Engineer, NASA EED-2</span><o:p></o:p></p>
<p><span style="font-size:12.0pt">Office: 301-851-8113 | <a href="mailto:Tyler.B.Stevens@nasa.gov">Tyler.B.Stevens@nasa.gov</a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> esip-semanticweb
<a href="mailto:esip-semanticweb-bounces@lists.esipfed.org"><esip-semanticweb-bounces@lists.esipfed.org></a> on behalf of Siri Jodha Khalsa via esip-semanticweb
<a href="mailto:esip-semanticweb@lists.esipfed.org"><esip-semanticweb@lists.esipfed.org></a><br>
<b>Sent:</b> Friday, January 10, 2020 4:08 PM<br>
<b>To:</b> <a href="mailto:esip-semanticweb@lists.esipfed.org">esip-semanticweb@lists.esipfed.org</a>
<a href="mailto:esip-semanticweb@lists.esipfed.org"><esip-semanticweb@lists.esipfed.org></a><br>
<b>Subject:</b> [EXTERNAL] Re: [esip-semantictech] NASA GCMD Keywords Version 9.0 Released (2019-11-12)</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p style="background:white">I'm curious whether the ESIP semantic community has any opinions on these two controlled vocabularies.
<o:p></o:p></p>
<p style="background:white">One question I have is why a measurement keyword list was necessary when GCMD already has the science keywords (a source for the original SWEET). i.e. why not integrate measurements (which are represented as variables in the science
keywords) into the science keywords?<o:p></o:p></p>
<p style="background:white"><o:p> </o:p></p>
<p style="background:white">the data format list is even more perplexing to me. "incidence angle file" is a format? Georeferenced TIFF in addition to GeoTIFF? DV? (digital value?) is a format? KML as well as OGC KML? ASCII and text (what about unicode?) DEM,
if this refers to digital elevation models with a .DEM extension from USGS, are ASCII files.
<o:p></o:p></p>
<p style="background:white"><o:p> </o:p></p>
<p style="background:white">Many formats are subtypes of other formats listed. Wouldn't a better approach be to list the
<i>encodings</i> (a much smaller list, which would tell users how to read the data with software) and then add the conventions that have been applied (e.g. CF for netCDF or GRIB for binary). For the encodings list, why not start with mime types?<o:p></o:p></p>
<p style="background:white"><o:p> </o:p></p>
<p style="background:white">sjs<o:p></o:p></p>
<p style="background:white"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white">On 11/12/19 5:00 PM, Stevens, Tyler B. (GSFC-423.0)[Stinger Ghaffarian Technologies] via esip-semanticweb wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p style="margin-right:9.0pt;text-align:justify;background:white"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">The NASA Global Change Master Directory (GCMD) staff is pleased to announce the release of the GCMD keywords version
9.0. Version 9.0 consists of two new keyword schemes: (1) Measurement Name and (2) Granule Data Format. </span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><o:p> </o:p></p>
<p style="margin-right:9.0pt;text-align:justify;background:white"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">The
</span><a href="https://gcmdservices.gsfc.nasa.gov/kms/concepts/concept_scheme/MeasurementName/?format=csv"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">Measurement Name</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
list is a preliminary set of (~100) keywords that represent an observable property, usually geophysical, geo-biophysical, physical, or chemical. The
</span><a href="https://gcmdservices.gsfc.nasa.gov/kms/concepts/concept_scheme/GranuleDataFormat/?format=csv"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">Granule Data Format</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
list of keywords represent the format of the data that is distributed by the data center. </span><o:p></o:p></p>
<p style="mso-margin-top-alt:12.0pt;margin-right:9.0pt;margin-bottom:12.0pt;margin-left:0in;text-align:justify;background:white">
<span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">The keywords help facilitate the classification and discovery of Earth Science data by providing a rich vocabulary for characterizing the data. The GCMD keywords are used by hundreds
of data providers worldwide for categorizing the ~33,000 records stored in the</span><a href="http://earthdata.nasa.gov/cmr"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">Common Metadata Repository</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">.</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">For more information about the keywords and how to access them, please visit the</span><a href="https://earthdata.nasa.gov/about/gcmd/global-change-master-directory-gcmd-keywords"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">Keyword Landing Page.</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> Questions about the keywords can be submitted to
</span><a href="mailto:support@earthdata.nasa.gov"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">support@earthdata.nasa.gov</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">or directed to Valerie Dixon at
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#1155CC"><a href="mailto:valerie.dixon@nasa.gov">valerie.dixon@nasa.gov</a></span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">.</span>
<br>
<br>
<o:p></o:p></p>
<pre style="background:white">_______________________________________________<o:p></o:p></pre>
<pre style="background:white">esip-semanticweb mailing list<o:p></o:p></pre>
<pre style="background:white"><a href="mailto:esip-semanticweb@lists.esipfed.org">esip-semanticweb@lists.esipfed.org</a><o:p></o:p></pre>
<pre style="background:white"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.esipfed.org_mailman_listinfo_esip-2Dsemanticweb&d=DwMD-g&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=ClhE-fOXVws9KIK2m9XESFX-807X65oCtO3rphfxx2E&m=EG8U-BXyuZvGMMlWA_PVLxkC6Vh4j5BTuWQEPBKdXyc&s=TP_AfLZv4ZRU2M_bc5sHF-yPGcMAmyEN8XdcAbpPwYE&e=">https://lists.esipfed.org/mailman/listinfo/esip-semanticweb</a><o:p></o:p></pre>
</blockquote>
<pre style="background:white">-- <o:p></o:p></pre>
<pre style="background:white">Siri-Jodha Singh KHALSA, Ph.D., SMIEEE<o:p></o:p></pre>
<pre style="background:white">National Snow and Ice Data Center<o:p></o:p></pre>
<pre style="background:white">University of Colorado<o:p></o:p></pre>
<pre style="background:white">Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976<o:p></o:p></pre>
<pre style="background:white"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__cires.colorado.edu_-7Ekhalsa&d=DwMD-g&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=ClhE-fOXVws9KIK2m9XESFX-807X65oCtO3rphfxx2E&m=EG8U-BXyuZvGMMlWA_PVLxkC6Vh4j5BTuWQEPBKdXyc&s=VTw7ReildGiAwFGiqYlC1SoansU6OP0UWrnir7pynrk&e=">http://cires.colorado.edu/~khalsa</a><o:p></o:p></pre>
<pre style="background:white"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__orcid.org_0000-2D0001-2D9217-2D5550&d=DwMD-g&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=ClhE-fOXVws9KIK2m9XESFX-807X65oCtO3rphfxx2E&m=EG8U-BXyuZvGMMlWA_PVLxkC6Vh4j5BTuWQEPBKdXyc&s=nP-FaYmd88tiUvCLMjekdWMhICOYNP2L7Mxn6ya3ANQ&e=">http://orcid.org/0000-0001-9217-5550</a><o:p></o:p></pre>
</div>
</div>
</div>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Siri-Jodha Singh KHALSA, Ph.D., SMIEEE<o:p></o:p></pre>
<pre>National Snow and Ice Data Center<o:p></o:p></pre>
<pre>University of Colorado<o:p></o:p></pre>
<pre>Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__cires.colorado.edu_-7Ekhalsa&d=DwMG-g&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=wGUjZntCVZd_0RfHkUyi5nt60hYIHfuz8TuYqGTTTOIC3GyzxW-xjOqs-Ck3ToTH&m=oz9a0L5ETVGh6EuDL7NBLNbHUlgh5DEMi4hdFdk9VCM&s=VrxEOXeDhOwA38mZ_XNhvr2y2zNFLvjOB7zQajoV1Ng&e=">http://cires.colorado.edu/~khalsa</a><o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__orcid.org_0000-2D0001-2D9217-2D5550&d=DwMG-g&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=wGUjZntCVZd_0RfHkUyi5nt60hYIHfuz8TuYqGTTTOIC3GyzxW-xjOqs-Ck3ToTH&m=oz9a0L5ETVGh6EuDL7NBLNbHUlgh5DEMi4hdFdk9VCM&s=Nv00kv7GRaeDFSOrceGWguDGN1Mn9-i-t4DFTN04VLk&e=">http://orcid.org/0000-0001-9217-5550</a><o:p></o:p></pre>
</div>
</body>
</html>