Dear @ethanrd I would favour simplicity. At the moment, we have two categories in the conformance document. (1) Recommendations to do something. A recommendation not to do something is a deprecation. The CF checker gives warnings for recommendations (including deprecations) that are not met. (2) Requirements to do something. A requirement not to do something is a prohibition. The CF checker gives errors for requirements (including prohibitions) which are not met. I feel that this is sufficient, provided we make sure all the recommendations and requirements in the standard are included in the conformance document. We can't foresee what will happen in future versions of the convention.
Maybe we should make the https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/314__;!!G2kpM7uM-TzIFchu!kzzdQFSH_Yxz7wNdYsjWAGGce-DvvXwqHyyu3QDxqbG6W2w4kgdAykaEKSmqo7lm7FGj6Q8sg2A$ deprecation into a prohibition instead i.e. disallow (as you say) the flawed old version of "sigma over z"? Then the checker would give an error if it detects it. We could make clear in stating the requirement that it applies to new data (from now on), and does not invalidate existing data (although such data may unavoidably be problematic). Best wishes 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/328*issuecomment-847808514__;Iw!!G2kpM7uM-TzIFchu!kzzdQFSH_Yxz7wNdYsjWAGGce-DvvXwqHyyu3QDxqbG6W2w4kgdAykaEKSmqo7lm7FGjRfgwcP4$ 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].
