<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 26, 2007, at 1:25 PM, Joe Cheng wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Helvetica Neue'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Or how about a separate member that says what time zone is being<br>used? This way there's no data duplication.<br></span></blockquote></div><div><br class="webkit-block-placeholder"></div><div>The only question that comes up is then you have to detect whether the "old-style" date is in fact one of these unusual beasts that has the time-zone tacked in. Maybe not a big deal, but you'd then have the question of whether the additional time-zone metadata is an affirmation of the built-in time zone, or a further adjustment to it.</div><div><br class="webkit-block-placeholder"></div><div>I think I prefer the separate field because it clearly delineates the meanings of the fields. One is "server-specific meaning", and one is GMT. Each is fully independent and parseable without regard to the other (if the client doesn't want to regard one or the other).</div><div><br class="webkit-block-placeholder"></div><div><blockquote type="cite"><member><br> <name>dateCreated</name><br> <value><br> <dateTime.iso8601>20070623T01:22:18</dateTime.iso8601><br> </value><br></member><br><member><br> <name>dateCreatedTimeZone</name><br> <value>+08:00</value><br></member></blockquote></div></body></html>