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/.
#95: Development of CF 1.5 Data Model -----------------------------+---------------------------------------------- Reporter: markh | Owner: [email protected] Type: task | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by taylor13): Dear Jonathan and all, I agree that "precedence" has the meaning you ascribe to it, but I think this was a mistake. I suggest that "When an attribute appears both globally and as a variable attribute, the variable's version has precedence." should be replaced with a statement that global attributes should contain only information that applies to all variables in the file, whereas variable attributes with the same name should contain additional information applying to the specific variable. If this were done, files constructed correctly would never have conflicting information stored in global and variable attributes of the same name. In this case the user could safely make use of both. I think saying that the variable attribute supersedes the global attribute information is asking for trouble, as the casual user may not be aware that the global attribute should be ignored in this case. Most users would, I think, incorrectly assume that both the global attribute information and the variable attribute information were valid. [Like me they might have missed that "precedence" statement in the conventions document.] Does anyone know of files where a global attribute does not apply to a variable that has an attribute of the same name? best regards, Karl -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:95> 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.
