Dear @Dave-Allured 

Thanks for repeating the proposal and preparing the pull request. I agree with 
the choices you propose and the wording. After the deprecation of year zero in 
reference date/time, I'd like to add the following for the avoidance of doubt. 
Alternatively it could be inserted after "prohibited for certain calendars, as 
noted below."

> Date/times in zero or negative years are prohibited by calendars which 
> prohibit these years in the reference date/time. In these calendars, it is an 
> error to store or decode a time coordinate value for a date/time earlier than 
> 1-1-1 0:0:0, regardless of the reference date/time in the time `units`.

I also agree with your deprecation of the year 0 climatological convention, but 
it is stronger than what section 7.4 currently says, which is, "We do not 
recommend this convention." That sounds the same, but it's not currently noted 
in the conformance document for section 7.4. Therefore I think we must either 
not deprecate it in 4.4, or deprecate it in 7.4, to be consistent.

We also need to include corresponding changes to the conformance document in 
the pull request. I think it's in the same repo now, isn't it, for this reason?

Re the question from @jswhit, I too asked about year zero in the proleptic 
Gregorian calendar earlier. You said that year zero is conventionally allowed 
in that calendar. I'm happy to take your word for that.

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/298*issuecomment-794196013__;Iw!!G2kpM7uM-TzIFchu!jdXoT0jVFemfPAB8X1WZGimMxMLxSYiLc4JNdS9DXY5IS-YA9ufNE7LgnEn0Lq8Mb0vWDiym0sM$
 
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