agree with @JonathanGregory on deprecating (rather than disallowing) years < 1 in `standard` and `julian` calendars (where I interpret this to refer to the year in the reference time stamp).
I'm not sure about the proposal to redefine `gregorian` : it is currently defined as mixed Gregorian/Julian which appears OK. I don't have a clear opinion on this. Concerning what udunits2 supports: the command line tool treats `0-0-0` as equivalent to `1-1-1` and `-1-1-1` as being 366 days apart. udunits2 uses a mixed Gregorian/Julian calendar. The library does accept arbitrary years and ISO basic format. This means that `19850101` is equivalent to `1985` or `1985-01-01`. This means that the `-MM` is not optional when you want to reference years with more than 4 digits. It looks like a rather fragile approach to me, and documentation is lacking. Does anyone know of people wanting to use the ISO basic format, with no delimiters in the date? Could we simplify the specification (and parsing requirements) by insisting on the ISO "extended format", which has `-` as a delimiter in the date and `:` in the time? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/298#issuecomment-704395704 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
