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 bnl): ... but this distinction would be difficult to interpret once you mix and match variables which have previously inherited attributes. In practice you couldn't distinguish between the importance and meaning of these attributes down the line, so if you can't distinguish them, they have no *absolute* semantic meaning. I've suggested previously a compromise which would allow software in a specific workflow to read such extra semantic meaning, but one couldn't rely on all software understanding such meaning, since in effect CF would then have to support the semantics of all possible workflows. So, I have no problem if you give variable A two attributes, one of which is marked in such a way as to indicate it is inherited when you read the file, but the CF data model should be agnostic of that, even if *your* software is not. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:91> 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.
