Regarding the recent revisions to the "principles", I like the revisions you've made in https://github.com/cf-convention/cf-conventions/issues/273#issuecomment-649396973 , and I think there are no references to "files" now (only to "datasets"), unless I've missed something. The suggestion by Philip in https://github.com/cf-convention/cf-conventions/issues/273#issuecomment-649414779 sounds like a good one to me.
And I think we should consider whether we could do something to identify the CF attributes in a file, maybe simply listing the ones appearing in the file in the "Conventions" attribute, enclosed in parentheses (e.g., ``Conventions = "CF1.8 (standard_name, units, coordinates, bounds, calendar)"``. Of course this would not be particularly elegant, but would work. If someone wants to pursue this or related suggestions, I guess that discussion should be moved elsewhere. As for a need to make it easy for folks to distinguish the CF attributes from others, consider the following analogy: Suppose authors submitting a paper to British journal are required to write it in English, but are allowed to include short passages in a foreign language (without translation). Many readers literate in only English would be able to understand most of the article (and would likely skip over the sections in a foreign language). We would not expect the author to point out that the foreign language bit was not English. We expect those reading netCDF files and interpreting the metadata to do the same thing: recognize what is CF and what is not, and be able to interpret the CF attributes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/273#issuecomment-649624598 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
