In https://urldefense.us/v3/__https://github.com/cf-convention/discuss/issues/155__;!!G2kpM7uM-TzIFchu!mfJaB4CUzVG70gMwLsn4NCDOHB_EztOTEMDN2iHwJ1ozSQQSyUZf2ptPvesV5t40hwcl518oMxw$ @jonathanlilly has pointed out that the current text of section 3.3 might appear to mean that a given `standard_name` can appear only once in any file. The text follows the description of `long_name`, whose usage is "is completely ad-hoc." It continues
> For some applications it would be desirable to have a more definitive > description of the quantity, which would allow users of data from different > sources (some of which might be models and others observational) to determine > whether quantities were in fact comparable. For this reason an optional > mechanism for uniquely associating each variable with a standard name is > provided. Also it's written with "would" as though standard names are hypothetical, because this text was written at the start of CF when they were a new idea. I propose that we replace the above text with the following, in which I have put new words in **bold**: > For **many** applications it **is** desirable to have a more definitive > description of the quantity, which **allows** users of data from different > sources (some of which might be models and others observational) to determine > whether quantities **are** in fact comparable. For this reason **each > variable may optionally be given a "standard name", whose meaning is defined > by this convention.** Comments are welcome. I believe that this does not change the intended meaning of the convention, but only clarifies the text. Therefore it can be treated as a remedy for a defect, so this proposal will be accepted in three weeks (on 2nd June) if there are no objections. Jonathan -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/366__;!!G2kpM7uM-TzIFchu!mfJaB4CUzVG70gMwLsn4NCDOHB_EztOTEMDN2iHwJ1ozSQQSyUZf2ptPvesV5t40hwcl9QLoxNk$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
