Re: [CF-metadata] [cf-convention/cf-conventions] Correction to the definition of "ocean sigma over z coordinate" in Appendix D (#314)
That sounds good to me, too. -- 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-828432982__;Iw!!G2kpM7uM-TzIFchu!gCLQZ35irkVAXBxrH8qj-6Fz8k-gkWmO9EUjXFYzaSLe9qoFZJ8oGNfCdWmW49C5QaEFjK9ju7c$ 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)
Yes, thanks, I agree with Klaus that we should deprecate it, so that a warning is given by the checker. I think we should also check its value, because even if deprecated it may be used by software. Jonathan -- 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-828432328__;Iw!!G2kpM7uM-TzIFchu!kLmKaDWzD01mXlJvP8vGGCgIlcuOLhSk24YXoM4N_zayQKS43V1FpxZpmMmvokP-FuqKG4a1jmw$ 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)
Another option would be to declare `nsigma` deprecated. This way it would be around for some time to come, but new data would avoid using it and it would be clear that that is correct. In a future release, such backward-incompatible changes could be bundled. For reference, I link here to [the Numpy deprecation policy](https://urldefense.us/v3/__https://numpy.org/neps/nep-0023-backwards-compatibility.html__;!!G2kpM7uM-TzIFchu!h-MRQLFC6twLFrV7lbOu_-sCZTYV4BOC-gq-k-aRSSm8Uv5QjEQIwhGxMrf9Z2EeDI8_n3C6L4k$ ) and [the Python deprecation policy](https://urldefense.us/v3/__https://www.python.org/dev/peps/pep-0387/*making-incompatible-changes__;Iw!!G2kpM7uM-TzIFchu!h-MRQLFC6twLFrV7lbOu_-sCZTYV4BOC-gq-k-aRSSm8Uv5QjEQIwhGxMrf9Z2EeDI8_wF3FdfI$ ) as examples of how other projects handle this kind of issue. -- 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-828411974__;Iw!!G2kpM7uM-TzIFchu!h-MRQLFC6twLFrV7lbOu_-sCZTYV4BOC-gq-k-aRSSm8Uv5QjEQIwhGxMrf9Z2EeDI8_otk1j20$ 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.
