> datetime Digest 17 Sep 2007 21:06:53 -0000 Issue 714 > > Re: [rt.cpan.org #23307] YYYY-MM-DD HH:MM:SS not a valid datetime > 6819 by: Joshua Hoblitt
> ----- Message from Joshua Hoblitt <[EMAIL PROTECTED]> on Mon, > > I haven't given RFC 3339 an in depth study but it appears to be a > significant simplification of ISO 8601:2000. As you note, it's not > really just a subset either as not all valid RFC 3339 formats are valid > ISO 8601 formats because of the time & date separator relaxation. It's > also not clear to me if independent date or time formats are allowed. > The ABNF is incorrect in that it doesn't allow for the "space" separator > in place of "T". > > I would be tempted to make a parser for this RFC live in a new > namespace, e.g. DateTime::Format::RFC3339, regardless of how much code > (and tests) are shared. It probably makes sense to bundle it with > DT:F::ISO8601 as well. I note that one specific standard that uses the simplified ISO 8601 notation with a blank in place of T is the ISO SQL standard (ISO/IEC 9075-2:2003). Of course, some DBMS use variations on the SQL standard notation too - IBM DB2 uses a full stop (period, dot) in place of the T or blank). -- Jonathan Leffler ([EMAIL PROTECTED]) STSM, Informix Database Engineering, IBM Information Management Division 4100 Bohannon Drive, Menlo Park, CA 94025-1013 Tel: +1 650-926-6921 Tie-Line: 630-6921 "I don't suffer from insanity; I enjoy every minute of it!"
smime.p7s
Description: S/MIME Cryptographic Signature
