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 markh): Replying to [comment:102 davidhassell]: > Good point about non-standard attributes (although I'm not sure how they relate to the global/data attribute debate). CF recognises that people use non-CF attributes and impart meaning into these which should be carried along with a dataset once it is extracted from a NetCDF file into the data model. So, consider a file which has a global attribute of 'responsible_authority' and two data variables, one with a data variable attribute of 'responsible_authority'. This key is not CF, the data model objective is just to preserve the information, not provide any CF insight into the interpretation. If two name spaces are used, one for global attributes and one for data variable attributes, this preservation becomes easy. Some parties in this discussion have favoured one attribute set, I presume with unique keys. In this case I am concerned that the information from the file related to this key cannot be stored in a Field instance. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:103> 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.
