I'm confused about one line, sorry if this is a basic misunderstanding: > Subsequent versions of the CF Conventions will not make invalid a compliant > usage of this or earlier versions of the CF terms and forms.
I understand we want/expect any CF tool to be able to read CF files from previous CF versions, so it makes sense that we don't want to invalidate those earlier files. But if I use an attribute name in my CF 1.8 compliant file, and then later (say CF 1.9) the CF standard (unknowingly of course) uses that same attribute for a specific purpose (incompatible with the purpose I used it for in my 1.8-compliant file), how will that not make my compliant usage invalid? How is this accidental re-purposing avoidable? I just can't figure out how any tools would implement that, without having a whole bunch of historical libraries for reading files from older versions of CF. -- 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-569992711 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].
