@graybeal I read and understand the sentence in question this way: A file that is compliant with a particular version of CF and contains a declaration of the CF version used is not made invalid by any later change to CF that would make the same file non-compliant if it was declared to use that later version. The fact that a change made in CF 1.9 invalidates a standard or non-standard practice in a file built using CF 1.8 doesn't make the CF 1.8 - compliant file invalid, as long as I have a **`Conventions`** attribute in the file that declares CF-1.8.
-- 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/207#issuecomment-570283481 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].
