[Standards-JIG] Communicating timezone information

[Maciek Niedzielski]

Chris Mullins wrote:
> Maciek Niedzielski Wrote:
> 
>> I'm looking for a way to communicate timezone information.
>> 1. JEP-0090 (jabber:iq:time) sends current time in... UTC.
> 
> I know in our SDK, we populate the <tz/> element with the following
> code:
> _tz = System.TimeZone.CurrentTimeZone.StandardName;

Even if this is a "standard name", I have to use google to know what
does "Pacific Daylight Time" mean. And I wouldn't be surprised if this
name would depend on your OS language, which makes things even harder.


> (A quick gander through the .Net 2.0 framework shows that although I can
> get the standard name for the current timezone, there's no way to
> construct a TimeZone instance from one of these standard names. This
> seems more than a little bit retarded.)

Maybe the translation issue is the reason.


> I don't see why we don't use the standard Xml time format here.

Probably because this protocol is sooooooooo old ;)
Its time format is different than in all other JEPs.

Maybe these are enough reasons to write a replacement?
New protocol would
1) follow JEP-0082 (Jabber Date and Time Profiles) to express current time
2) provide timezone offset in a standard format (like "[+|-]hh:mm" offset)

And PEP fans could publish the information (just the timezone, of course
;)) via PEP.

-- 
Maciek                       A: It's against natural order of reading.
 xmpp:machekku at uaznia.net   Q: Why is that?
 xmpp:machekku at chrome.pl   A: People answering above quoted text.
                          Q: What's the most annoying on newsgroups?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 257 bytes
Desc: OpenPGP digital signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20060825/616b1b25/signature.pgp