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): Replying to [comment:66 spascoe]: > The Data Model needs to differentiate between the encoding of attributes and attributes of model constructs. The encoding states how a field construct's attributes can be encoded and decoded into global and/or variable attributes. These rules would include how variable attributes override global attributes. > > Then the rest of the data model can ignore the distinction between global and variable attributes. Everything can be expressed in attributes of constructs. I don't think I agree with restatement in detail. The first paragraph more or less contradicts the second. Of course we have to have a "set of rules for the netcdf encoding" of the data model, and that includes describing the convenience method of using global attributes. That isn't the CF data model, it's the CF-netcdf encoding convention. The CF-data model itself ought to be agnostic about the encoding rules - which is what the second para says, I'm just trying to clarify the relationship between the first and second paragraph. > > That would seem to clarify the situation. It would also help disentangle the CF model from the format, which is what we are trying to do. Which it would with the understanding that we're dealing with two different sets of logic: the CF-netcdf convention and the CF data model. But there should be no expectation that a round trip from CF-netcdf via CF to CF-netcdf should necessarily preserve global attributes per se ... ... if providers wish to build software that do that, then that's fine, then they're building implementations of "site-specific-software" that are overloading CF with their own conventions ... which is perfectly fine! -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:67> 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.
