This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#96: Julian/Gregorian calendar name and constraints -----------------------------+---------------------------------------------- Reporter: Dave.Allured | Owner: [email protected] Type: enhancement | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: calendar time julian gregorian udunits -----------------------------+---------------------------------------------- Comment (by Dave.Allured): Replying to [comment:5 jonathan]: Yes, this is technically a proposal for a "new calendar". I should have said this more clearly in the introduction, sorry. My general rationale for the new calendar name is two-fold. The first purpose is simply to improve the quality of self-documentation of data sets. CF should have a simple way to declare explicitly and deliberately that the mixed Julian/Gregorian calendar is being used. Currently there is no standardized way to do this. The second purpose is to provide a transitional alternative, a mechanism to make it easier to deprecate previous calendar names and usage, where there can be a consensus that previous usage is bad practice or bad design. This new calendar name could be easily substituted for previous "inadequate" calendar names in many existing data sets, as needed, with no recomputation of time coordinates or other adjustments. With a reasonable alternative and the ability to retrofit existing data sets, some people may be able to accept more significant changes, such as removing the default calendar. I tried to explain this rationale in other words above, under "Requirement" and "Benefits". --Dave -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/96#comment:6> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
