<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:Monospace">
<p>Am Dienstag, 22. März 2011 23:26:18 schrieb Jeroen van Meeuwen (Kolab Systems):</p>
<p><span style="color:#008000">> I think you're mistaken in the perception that:</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> 20110322T220000</span></p>
<p></p>
<p><span style="color:#008000">I was thinking about using "2011-03-22T22:00:00", as the example</span></p>
<p><span style="color:#008000">above does not match the rules I've proposed in</span></p>
<p><span style="color:#008000">http://kolab.org/pipermail/kolab-format/2011-March/001237.html</span></p>
<p>But I guess this is irrelevant to the discussion in this thread.</p>
<p></p>
<p><span style="color:#008000">> to indicate a local time with is somehow ISO-8601 compliant. </span></p>
<p></p>
<p>As far as I can say it parses Appendix A. ISO 8601 Collected ABNF</p>
<p>of rfc3339. </p>
<p></p>
<p><span style="color:#008000">> Sure it is compatible with a selected paragraph, </span></p>
<p><span style="color:#008000">> but ISO-8601 specifically refers to either UTC *or* </span></p>
<p><span style="color:#008000">> local time plus the UTC offset, whenever the time is </span></p>
<p><span style="color:#008000">> included in the datetime (or in cases the offset is unknown, "-00:00" as</span></p>
<p><span style="color:#008000">> the offset).</span></p>
<p></p>
<p><span style="color:#008000">I do not have a copy of ISO-8601 at hand, do you?</span></p>
<p>In its absense, I have found strong hints </p>
<p>that it is okay to use the above form</p>
<p>without offset to indicate local time:</p>
<p> </p>
<p><span style="color:#008000">http://www.iso.org/iso/date_and_time_format</span></p>
<p><span style="color:#008000">has an example coming close:</span></p>
<p><span style="color:#008000"> Example: 2003-04-01T13:01:02 represents one minute and two seconds after one o'clock in the afternoon of 2003-04-01. </span></p>
<p></p>
<p><span style="color:#008000">In addition:</span></p>
<p><span style="color:#008000"> Specifications applying ISO 8601 can have a need to define the allowed </span></p>
<p><span style="color:#008000"> representation of the expressions in a certain data field. For instance a </span></p>
<p><span style="color:#008000"> specification might want to define that a certain field containing the date </span></p>
<p><span style="color:#008000"> and time of an event should do so in the format: YYYYMMDDhhmm with the </span></p>
<p><span style="color:#008000"> exclusion of all other formats allowed by ISO 8601</span></p>
<p></p>
<p><span style="color:#008000">http://en.wikipedia.org/wiki/ISO_8601 writes:</span></p>
<p><span style="color:#008000"> If no UTC relation information is given with a time representation, the time is assumed to be in local time.</span></p>
<p></p>
<p><span style="color:#008000">And Qt 4.7.2 accepts it:</span></p>
<p><span style="color:#008000">QDateTime time2 = QDateTime::fromString("1996-12-20T00:39:57", Qt::ISODate);</span></p>
<p></p>
<p><span style="color:#008000">> http://www.w3.org/TR/xmlschema-2/#dateTime</span></p>
<p></p>
<p>also writes:</p>
<p>'"Local" or untimezoned times are presumed to be the time in the timezone of some unspecified locality'</p>
<p></p>
<p>'zzzzzz (if present) represents the timezone (as described below).'</p>
<p></p>
<p>which all allow the absense of the offset for good.</p>
<p></p>
<p>Best,</p>
<p>Bernhard</p>
<p></p>
<p></p>
<p></p>
<p>-- </p>
<p>Managing Director - Owner: www.intevation.net (Free Software Company)</p>
<p>Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.</p>
<p>Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998</p>
<p>Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner</p>
</body></html>