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 [email protected]): Martin: I can not speak for all, but from posting and reading board and trac messages for a while, there is a resistance to the use of software- language-like conventions. Personally, I believe this overarching thinking has served the standard and the community that uses the standard well. For this particular enhancement, while the complexity of the software parsing the standard_name attribute is increased, the new syntax is a natural extension of the exising convention and likely to minimize confusion. For these reasons, I think the approach and latest verbage change to the CF standard proposed is a conservative and reasonable path forward. I will include the change to the CF standard in this post for completeness: In paragraph 3.3 Standard Names, right after this existing statement of: "A standard name is associated with a variable via the attribute standard_name which takes a string value comprised of a standard name optionally followed by one or more blanks and a standard name modifier (a string value from Appendix C, Standard Name Modifiers)." Include the following statement in the same paragraph: "In the case where more than one data variable, each with a standard name, references an ancillary data variable (see Section 3.4, “Ancillary Data”) for the same reason (e.g. status_flag), the standard_name attribute for the ancillary data variable is composed of a blank-separated list of each unique standard name followed by one or more blanks and a standard name modifier." very respectfully, randy -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:24> 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.
