<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 26, 2007, at 12:54 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; ">Either that or a quorum of the blog client and server implementers<br>need to band together and create a profile that removes the ambiguity<br>from MetaWeblog. I personally would be happy to contribute to that<br>effort if others agree it is a good idea.</span></blockquote></div><div><br class="webkit-block-placeholder"></div><div>I think this is a good idea and I'm for anything that will fix the problem long-term, as long as clients are given a chance to accommodate it. It also seems like something that all of the server providers need to sign off on at once, or else it's not very useful.</div><div><br class="webkit-block-placeholder"></div><div>A compromise solution that would muddy the XML namespace but would at least allow for all parties to "win" would be to add a separate XML attribute for clients who want the GMT time explicitly.</div><div><br class="webkit-block-placeholder"></div><div><div> <member><name>dateCreated</name><value><dateTime.iso8601>20070623T01:22:18</dateTime.iso8601></value></member></div> <member><name>wp_dateCreated</name><value><dateTime.iso8601>20070623T06:22:18</dateTime.iso8601></value></member></div><div><br class="webkit-block-placeholder"></div><div>This would enable WordPress to both lead by example and stay with the rest of the pack until they catch up. And the namespace expansion would be consistent with other WordPress extensions that are currently being added.</div><div><br class="webkit-block-placeholder"></div><div>(This might fall into that elusive "more ingenious solution" category I was alluding to)</div><div><br class="webkit-block-placeholder"></div><div>Daniel</div><div><br class="webkit-block-placeholder"></div></body></html>