[JDEV] Route tag spec proposal..

Colin Davis davisfamily at mediaone.net
Mon Oct 11 13:15:51 CDT 1999

"Jon A. Cruz" wrote:

>   <node id="jabber:jabbertransport://jabber.org/" received="19991004T23:35:54"
> sent="19991005T06:35:55" timezone = "-0700 (PDT)">
> or
>   <node id="jabber:jabbertransport://jabber.org/" received="19991004T23:35:54"
> sent="19991005T06:35:55" timeoffset="-0700" timezone = "PDT">
> Here are my clarifications. Note the distintion between 'must' and 'should'.
> 1) All times must be transmitted in GMT.
> 2) A timezone should be included
> 3) A timezone must include it's hours offset from GMT.
> 4) A timezone should include a letter designation, if known.

I agree with you most of the way, however let me make one suggestion: 

If timezone information is not sent, the client defaults to the last
timezone information it had recieved from that person (ie, in a previous

  This has the effect of reducing the size of the messages sent (a good
thing), as there is no reason to send the information if nothing has
  This would still solve the problem of messages across different time
zones, as when you changed the time zone, the jabber client would then
include the new timezone on the next message to you. 

  <node id="jabber:jabbertransport://jabber.org/"
 sent="19991005T06:35:55" timeoffset="-0700" timezone = "PDT">

[Then in the next message: ]

   <node id="jabber:jabbertransport://jabber.org/"

[Severalmore messages of Type II, then the user sending the messages
changes to a new Timezone. In the next message:]

  <node id="jabber:jabbertransport://jabber.org/"
 sent="19991005T06:36:02" timeoffset="-0600" timezone = "CDT">

For every message in the middle, you have saved a little bandwith. If a
still chooses to send information in every message, the recieving
clients would accept it, as per your proposal.

Colin Davis

More information about the JDev mailing list