Dear Gwyn,

Many thanks for your query. You are right that there should not be any white 
space within a standard name and if you do find examples of this, please 
continue to report them to the mailing list and I will correct them as part of 
the regular updates to the standard name table.

There is indeed a white space in v36 of the table (both html and xml versions) 
in the following name:
<entry id="rate_of_ hydroxyl_radical_destruction_due_to_reaction_with_nmvoc">
Martin Juckes has also emailed me about this one and it will be corrected in 
the next update, scheduled for November 15th.

Regarding the alias entries where white space appears, you are correct that 
this has been done purely for backwards compatibility. The misspelt names were 
present in the table for about six months in 2008 (versions 8 – 10) but were 
corrected in v11 onwards. When new data are being written, the current version 
of a standard name as it appears in the most recent version of the table should 
always be used. However, aliases are retained so that any previously written 
data are not suddenly invalidated due to changes such as spelling corrections.

Best wishes,
Alison

------
Alison Pamment                                                       Tel: +44 
1235 778065
Centre for Environmental Data Analysis         Email: 
[email protected]<mailto:[email protected]>
STFC Rutherford Appleton Laboratory
R25, 2.22
Harwell Campus, Didcot, OX11 0QX, U.K.


From: CF-metadata [mailto:[email protected]] On Behalf Of Gwyn 
Fireman
Sent: 31 October 2016 22:15
To: [email protected]
Subject: [CF-metadata] White space in CF standard names

The CF conventions document states: "A standard name contains no 
whitespace<http://cfconventions.org/cf-conventions/cf-conventions.html#standard-name>".

Yet the v36 name 
table<http://cfconventions.org/Data/cf-standard-names/36/src/cf-standard-name-table.xml>
 (and earlier) specifies the following entry and alias names containing white 
space:

  <entry id="rate_of_ hydroxyl_radical_destruction_due_to_reaction_with_nmvoc">
  <alias id="mole_fraction_of_chlorine dioxide_in_air">
  <alias id="mole_fraction_of_chlorine monoxide_in_air">
  <alias id="mole_fraction_of_dichlorine peroxide_in_air">
  <alias id="mole_fraction_of_hypochlorous acid_in_air">

I can understand keeping the aliases for backwards compatibility, but shouldn't 
the entry name be corrected?



--

Ms Gwyn Fireman, SAIC

Ocean Ecology Laboratory

NASA/GSFC Code 616 (mail 616.2)

Building 28 Room W161A

301-286-8910
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

Reply via email to