<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>All,</p>
<p><br>
</p>
<p>Last summer ESDIS conducted a <a moz-do-not-send="true"
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):</p>
<p>
<blockquote type="cite">
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">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.</p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"> </p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">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>. </p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"> </p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">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).</p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"> </p>
<p style="margin: 0px; padding: 0px; color: rgb(0, 0, 0);
font-family: arial, helvetica, sans-serif; font-size:
13.3333px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">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</p>
</blockquote>
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.<br>
</p>
<p><br>
</p>
<p>Cheers,</p>
<p>SiriJodha<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/14/20 4:46 PM, Stevens, Tyler B.
(GSFC-423.0)[Stinger Ghaffarian Technologies] wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BL0PR0901MB310512AD99C26F184871F343CF340@BL0PR0901MB3105.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
<div style="font-size: 12pt; color: rgb(0, 0, 0);">
<pre cols="72" style="color: rgb(50, 49, 48);"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">Siri-Jodha,</span><span style="font-family: Calibri, Helvetica, sans-serif;">
</span><div style="font-family: Calibri, Helvetica, sans-serif;">
</div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">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>
</div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">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, </span><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">and we can add interested folks </span></div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">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 </span><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">community sourced names to further describe variable </span></div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">data. </span></div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">
</span></div><div style=""><font face="Calibri, Helvetica, sans-serif">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:</font></div><div style=""><font face="Calibri, Helvetica, sans-serif"><i>As a user, I want to search for collections with granules that have a specific data format (e.g., NetCDF, HDF5, etc). </i>
</font></div><div style=""><font face="Calibri, Helvetica, sans-serif">
</font></div><div style=""><font face="Calibri, Helvetica, sans-serif">The initially discussion here has been very helpful. </font></div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">
</span></div><div style="font-family: Calibri, Helvetica, sans-serif;"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;">Thanks,</span></div></pre>
</div>
<div id="Signature">
<span style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt;"></span>
<span style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt;"></span>
<div style=""><span style="font-family: Calibri, Helvetica,
sans-serif; font-size: 12pt;"></span>
<div style="">
<span style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt;"></span>
<p style="font-family:Calibri,sans-serif; font-size:11pt;
margin:0in 0in 0.0001pt">
<span style="font-size:12pt;
font-family:Calibri,Helvetica,sans-serif">Tyler Stevens</span><span
style="font-size:13.3333px"><br>
</span><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt">KBR | </span><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt">Senior Discipline Engineer</span><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt">,
</span><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt">NASA EED-2</span></p>
<p style="font-family:Calibri,sans-serif; font-size:11pt;
margin:0in 0in 0.0001pt">
<span style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt;"></span><span style="font-size:12pt;
font-family:Calibri,Helvetica,sans-serif">Office:
301-851-8113 | </span><span
style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt"><a class="moz-txt-link-abbreviated" href="mailto:Tyler.B.Stevens@nasa.gov">Tyler.B.Stevens@nasa.gov</a></span></p>
<font style="font-family:Tahoma; font-size:13px" size="2"
face="Arial"><a
href="https://mail02.ndc.nasa.gov/owa/redir.aspx?C=V8CgRYg3bQhQJTfp1SZy8qz17zr57afdr3RPnU2Q1JJ5D_SfSAfVCA..&URL=http%3a%2f%2fgcmd.nasa.gov%2f"
target="_blank" moz-do-not-send="true"><span
style="color:blue"></span></a></font></div>
</div>
<div>
<div style="font-family:Calibri,Helvetica,sans-serif;
font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
esip-semanticweb
<a class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-abbreviated" href="mailto:esip-semanticweb@lists.esipfed.org">esip-semanticweb@lists.esipfed.org</a>
<a class="moz-txt-link-rfc2396E" 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)</font>
<div> </div>
</div>
<div style="background-color:#FFFFFF">
<p style="margin-top: 0px; margin-bottom: 0px;">I'm curious
whether the ESIP semantic community has any opinions on
these two controlled vocabularies.
<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">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?</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">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.
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">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?<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">sjs<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<div class="x_moz-cite-prefix">On 11/12/19 5:00 PM, Stevens,
Tyler B. (GSFC-423.0)[Stinger Ghaffarian Technologies] via
esip-semanticweb wrote:<br>
</div>
<blockquote type="cite"><b style="font-weight:normal">
<p dir="ltr" style="margin-top: 0px; margin-bottom:
0px;line-height:1.38; margin-right:9pt;
text-align:justify; margin-top:0pt; margin-bottom:0pt">
<span style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">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></p>
<br>
<p dir="ltr" style="margin-top: 0px; margin-bottom:
0px;line-height:1.38; margin-right:9pt;
text-align:justify; margin-top:0pt; margin-bottom:0pt">
<span style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">The
</span><a
href="https://gcmdservices.gsfc.nasa.gov/kms/concepts/concept_scheme/MeasurementName/?format=csv"
moz-do-not-send="true"><span style="font-size:12pt;
font-family:Arial; color:#1155cc; font-weight:400;
text-decoration:underline">Measurement Name</span></a><span
style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400"> 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"
moz-do-not-send="true"><span style="font-size:12pt;
font-family:Arial; color:#1155cc; font-weight:400;
text-decoration:underline">Granule Data Format</span></a><span
style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400"> list of keywords
represent the format of the data that is distributed
by the data center. </span></p>
<p dir="ltr" style="margin-top: 0px; margin-bottom:
0px;line-height:1.38; margin-right:9pt;
text-align:justify; margin-top:12pt;
margin-bottom:12pt">
<span style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">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"
moz-do-not-send="true"><span style="font-size:12pt;
font-family:Arial; color:#000000; font-weight:400;
text-decoration:underline">
</span><span style="font-size:12pt;
font-family:Arial; color:#1155cc; font-weight:400;
text-decoration:underline">Common Metadata
Repository</span></a><span style="font-size:12pt;
font-family:Arial; color:#000000; font-weight:400">.</span></p>
<span style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">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"
moz-do-not-send="true"><span style="font-size:12pt;
font-family:Arial; color:#000000; font-weight:400">
</span><span style="font-size:12pt; font-family:Arial;
color:#1155cc; font-weight:400;
text-decoration:underline">Keyword Landing Page.</span></a><span
style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400"> Questions about the
keywords can be submitted to </span><a
href="mailto:support@earthdata.nasa.gov"
moz-do-not-send="true"><span style="font-size:12pt;
font-family:Arial; color:#1155cc; font-weight:400;
text-decoration:underline">support@earthdata.nasa.gov</span></a><span
style="font-size:12pt; font-family:Arial;
color:#1155cc; font-weight:400">
</span><span style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">or directed to Valerie
Dixon at
</span><span style="font-size:12pt; font-family:Arial;
color:#1155cc; font-weight:400"><a
class="x_moz-txt-link-abbreviated"
href="mailto:valerie.dixon@nasa.gov"
moz-do-not-send="true">valerie.dixon@nasa.gov</a></span><span
style="font-size:12pt; font-family:Arial;
color:#000000; font-weight:400">.</span></b>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset>
<pre class="x_moz-quote-pre">_______________________________________________
esip-semanticweb mailing list
<a class="x_moz-txt-link-abbreviated" href="mailto:esip-semanticweb@lists.esipfed.org" moz-do-not-send="true">esip-semanticweb@lists.esipfed.org</a>
<a class="x_moz-txt-link-freetext" 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=" moz-do-not-send="true">https://lists.esipfed.org/mailman/listinfo/esip-semanticweb</a>
</pre>
</blockquote>
<pre class="x_moz-signature" cols="72">--
Siri-Jodha Singh KHALSA, Ph.D., SMIEEE
National Snow and Ice Data Center
University of Colorado
Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976
<a class="x_moz-txt-link-freetext" 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=" moz-do-not-send="true">http://cires.colorado.edu/~khalsa</a>
<a class="x_moz-txt-link-freetext" 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=" moz-do-not-send="true">http://orcid.org/0000-0001-9217-5550</a>
</pre>
</div>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Siri-Jodha Singh KHALSA, Ph.D., SMIEEE
National Snow and Ice Data Center
University of Colorado
Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976
<a class="moz-txt-link-freetext" href="http://cires.colorado.edu/~khalsa">http://cires.colorado.edu/~khalsa</a>
<a class="moz-txt-link-freetext" href="http://orcid.org/0000-0001-9217-5550">http://orcid.org/0000-0001-9217-5550</a>
</pre>
</body>
</html>