I agree with the desirability of distinguishing the default mixed Julian/Gregorian calendar from the Gregorian. It does not make sense to call dates "Gregorian" when they are earlier than the invention of the Gregorian calendar and don't conform to the Gregorian calendar rules. Redefining `gregorian` to have a distinct meaning from `standard` (=default), as @Dave-Allured proposes, would achieve that aim, but it would be backward-incompatible. It wouldn't invalidate any existing data, but it would mean that something which is presently legal would become illegal, and thus the change would potentially break existing software which doesn't check the version of the CF convention. This is not disastrous, but we don't usually make such changes to the convention. Hence I would prefer to deprecate `gregorian`, meaning that the CF checker would produce a warning if it was used in future. If there is a need for a Gregorian calendar which can only be used from 1582, we should introduce a new one for that purpose e.g. `strict_gregorian`. Is there a use-case for it? 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/319*issuecomment-812838600__;Iw!!G2kpM7uM-TzIFchu!m5KFxdY7J6KrX5fkGeDuC3kA02pREoL_evAITV59eCcnPR2pSZVb06a6zXPPjRNfaDWSpq4eR6Q$ 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].
