Re: [CF-metadata] [cf-convention/cf-conventions] Clarify and update CF rules for deprecating content (#328)

2021-05-26 Thread JonathanGregory
Dear all I'd like to repeat my earlier points that * We should make use of the existing list, namely the conformance document, for the purposes being discussed here - I don't think we need a new list. * We don't have to distinguish positive and negative categories, because they are

Re: [CF-metadata] [cf-convention/cf-conventions] Clarify and update CF rules for deprecating content (#328)

2021-05-26 Thread Klaus Zimmermann
I agree with what @ethanrd and @erget said, namely that we have errata and what I would call deprecations. I think it is quite important to actually remove deprecations at some point, preferably under a predictable policy, e.g. two versions after the initial deprecation. The reason is that

Re: [CF-metadata] [cf-convention/cf-conventions] Clarify and update CF rules for deprecating content (#328)

2021-05-26 Thread Daniel Lee
TLDR: My opinion is that the rules are sound for correcting errata, but we do not describe what to do in the case of deprecation. **This may not be necessary because we could consider deprecation normal care and feeding for the standard.** I do agree that we should have a list of deprecations