[CF-metadata] [cf-convention/cf-conventions] Clarify and update CF rules for deprecating content (#328)
The paragraph in the [CF rules document](https://urldefense.us/v3/__https://cfconventions.org/rules.html__;!!G2kpM7uM-TzIFchu!kARlSi-vy4vYD0KbbiHHsnruaUd23F_K5Va4APhRMDTprFm_kK76dOEvNF3CE-riPCTxVm7qfNw$ ) that discusses deprecation is focused on recent (or even the most recent) changes and versions. The rules for deprecation should be updated and clarified for other situations. For instance, a deprecation in issue #314 impacts text that has been part of CF since version 1.0. -- 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/328__;!!G2kpM7uM-TzIFchu!kARlSi-vy4vYD0KbbiHHsnruaUd23F_K5Va4APhRMDTprFm_kK76dOEvNF3CE-riPCTxZUZrca4$ 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Correction to the definition of "ocean sigma over z coordinate" in Appendix D (#314)
Hi all - The paragraph in the [rules document](https://urldefense.us/v3/__https://cfconventions.org/rules.html__;!!G2kpM7uM-TzIFchu!ka812U3rXTGiXhFTJ9vi-8Qw_cLVDhuM3XUJIQUi2EWbPJthBpBBagU3XRf6sgpMrh4w-Uane_Q$ ) that mentions deprecation seems focused on recent (or even the most recent) changes/versions. The paragraph starts with > If the change, once implemented in the conventions, subsequently turns out to > be materially flawed … a github issue should urgently be opened to discuss > whether to revoke the change. This “ocean sigma over z” deprecation would affect all pre-1.9 versions of CF. So there is no change to revoke. How to handle this situation seems unclear, though I lean towards agreement with @JonathanGregory and @pp-mo that it should be more granular than entire versions. Given all that, I think Jonathan’s text looks good. So as not to slow down the resolution of this issue, I propose we move further discussion of the rules around deprecation to a new issue. (I’ll create an issue shortly for further discussion.) -- 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-845466770__;Iw!!G2kpM7uM-TzIFchu!ka812U3rXTGiXhFTJ9vi-8Qw_cLVDhuM3XUJIQUi2EWbPJthBpBBagU3XRf6sgpMrh4wI3Wn7rs$ 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Correction to the definition of "ocean sigma over z coordinate" in Appendix D (#314)
> 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.
Re: [CF-metadata] [cf-convention/cf-conventions] Correction to the definition of "ocean sigma over z coordinate" in Appendix D (#314)
Dear Jonathan, Oh - what a difference a day makes! Thanks for the text. I think it is fine, but it states that it is still OK to produce CF-1.8 datasets if they don't contain this particular formula - is that what we want? I would have thought that the the creation of all new CF-1.8 datasets should be deprecated. David -- 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-844787747__;Iw!!G2kpM7uM-TzIFchu!lhB9iqaKmWBm-40r76k8kIBk5Fz32eOV4imo7SBRY8N54t4UgoUkoEXuRPLxyr7_Bg7xfLI2Q8o$ 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.
