Hello - the 20th May is here, and no further comments have arisen. Thanks to 
all for the interesting discussion - and especially to @johnwilkin for the 
excellent diagrams.

Before we merge, however, it is noteworthy that this issue has identified and 
corrected a fundamental flaw in the conventions (as opposed to a typographical 
error, for example), which I'm not sure has happened before. The 
[rules](https://urldefense.us/v3/__https://cfconventions.org/rules.html__;!!G2kpM7uM-TzIFchu!gMKxGr_7okqq-Pz4q2b5IyxMPX_wksNE2xQB8uuKNvnK5f8IT2UZ1LPFhT_cY1pnaqnn7fVInmY$
 ) on this state _The flawed version will be deprecated by a statement in the 
standard document and the conformance document. However, any data written with 
the flawed version will not be invalidated, although it may be problematic for 
users._

I am not sure in what form such a statement should take, or in where in the 
conventions document it should live. In any case, perhaps it should be 
considered as part PR #317?

@JonathanGregory  - do you agree the PR should be amended in this way? If so, 
would you like to propose some extra text?

Many thanks,
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-844145910__;Iw!!G2kpM7uM-TzIFchu!gMKxGr_7okqq-Pz4q2b5IyxMPX_wksNE2xQB8uuKNvnK5f8IT2UZ1LPFhT_cY1pnaqnn6eaOTLg$
 
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].

Reply via email to