This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#74: Allow sharing of ancillary variables among multiple data variables ---------------------------------------+------------------------------------ Reporter: [email protected] | Owner: [email protected] Type: enhancement | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: "ancillary data" "standard name modifiers" ---------------------------------------+------------------------------------ Comment (by graybeal): Jim wrote: "As near as I can tell, a standard name is a sort of type or class. It describes the contents of a variable by telling you what class of measurement it belongs to, but I think its reliable use must end there. If two variables share a standard name (or share a root standard name), it tells you about comparability, but it doesn't reliably tell you anything about linkage. ... Given all that, I don't have any problem with promoting status_flag and number_of_observations to the level of standard names." I agree with everything written above (and in the original post), except the last sentence. The motivation is not that the rest of the standard name provides traceability, it is to provide better descriptive information about the parameter (and perhaps its comparability) -- as was mentioned much earlier in this thread. (Is there ever a status flag that isn't a status flag about some measurement? Is there ever a number_of_observations that isn't a number of observations of something?) If the proposal is to allow appending _status_flag to a standard name, that would be OK, but not status_flag by itself (unless we require the relevant auxiliary information to be provided some other way). -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:28> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
