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): Definitions for the proposed new standard names might clear up confusion at this point. Sorry, I didn't read far enough back in the thread with enough care. The rewording that left us with "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)," created an uncertainty for me, namely: Are they really sharing metadata variables in the sense of the _same_ value applying to multiple primary variables? (As opposed to, say, allocating bits or something....) I see the answer is yes, and yet I still couldn't fathom the use case at first. So is the proposal now to eliminate the proposed text about ancillary variables, instead allowing these generic standard names as the complete answer? Or still to include the proposed text for ancillary variables? (In which case, can I propose instead the following wording :"In the case where the values of an ancillary data variable (see Section 3.4, "Ancillary Data") apply to multiple data variables simultaneously, the standard_name attribute..." ?) I withdraw my absolute reservation about promoting these to standard names, but assume it will be required to specify the variables to which the-variable-with-one-of-these-standard-names-applies. (Geez, I know that's unparseable, but can't fix it...) Otherwise you have a free- floating standard name with no effective means to understand what it really means. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:30> 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.
