> I would have thought that the the creation of all new CF-1.8 datasets should > be deprecated.
Just listening in here + heard something that affects us, (i.e [Iris](https://urldefense.us/v3/__https://scitools-iris.readthedocs.io/en/latest/__;!!G2kpM7uM-TzIFchu!jWRiABD_PTt6C61OHYUxf8u45uf71vQWmdarcpSwp3o53rB7-DY-gUflcQIdcyIFXO_ATZZNdaY$ )). I think that disallowing *any* creation of datasets using older conventions would be problematic for us, likewise maybe anyone who writes generic CF handling code. So, Iris nows support "most" of CF 1.7 for loading : We therfore aim to be CF-1.7 compliant and **that is the version level that we state in our output datafiles**. Although we still don't support **_all_** of CF-1.7 (even), that is the level we are currently notionally aspiring to. In particular it is **the lowest convention version consistent with any output we may currently produce**. So for us, stating CF-1.7 for output data means "you won't find anything in here that is not described by CF-1.7". For our _users_, i.e. from the point of view of an individual or software tool interpreting the data, this is the statement that most usefully describes what that data might contain. So, I think it would be _unhelpful_ for us to state compliance with a later version (e.g. 1.8), even though that is consistent with out outputs, if our outputs still contain **_no_** CF-1.8 -level features. We would move to stating CF-1.8, only when our output code adopts some CF-1.8 concepts, and so requires that level to be correctly understood. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/314*issuecomment-844942383__;Iw!!G2kpM7uM-TzIFchu!jWRiABD_PTt6C61OHYUxf8u45uf71vQWmdarcpSwp3o53rB7-DY-gUflcQIdcyIFXO_ASIQuA2w$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
