Dear Chris et al.
I may have missed it - are you proposing a change or a clarification to the
text of the CF standard document?
Best wishes and thanks
----- Forwarded message from Chris Barker <chris.bar...@noaa.gov> -----
> Date: Wed, 21 Sep 2016 12:52:48 -0700
> From: Chris Barker <chris.bar...@noaa.gov>
> To: Nan Galbraith <ngalbra...@whoi.edu>
> CC: "firstname.lastname@example.org" <email@example.com>
> Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol
> 161, Issue 3
> On Tue, Sep 20, 2016 at 5:45 AM, Nan Galbraith <ngalbra...@whoi.edu> wrote:
> > Can we recommend the use of ISO-compatible date strings, with
> > the caveat that time zone should always be included?
> Yes, we really should do that (though it's an offset that is specified, not
> a time zone)
> It's unfortunate that ISO defaults to local time, and that seems to be
> > non-negotiable.
> yup :-(
> This is what we use in the OceanSITES implementation of CF. Obviously,
> > it won't solve everyone's needs,
> I'm trying to see whos needs it wouldn't suit folks may well want local
> time, rather than UTC, but having it be unspecified does no one any good.
> and specifying times in "true" local time, with DST baked in is simply a
> nightmare for everyone --- it really, really should be discouraged!
> Christopher Barker, Ph.D.
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
> CF-metadata mailing list
----- End forwarded message -----
CF-metadata mailing list