[Standards-JIG] RE: Timed presence events

Peter Saint-Andre stpeter at jabber.org
Wed Mar 16 18:14:32 UTC 2005

On Tue, Mar 08, 2005 at 12:02:36PM +0100, Ralph Meijer wrote:
> On Tue, Mar 08, 2005 at 11:28:29AM +0100, Jean-Louis Seguineau wrote:
> > [..]
> > 
> > My question was more targeted at the protocol level. There are other
> > contexts where having a way to indicate the time boundary of a status, or an
> > activity, are precious. And this information may be applied to other
> > application than just the interactive IM.
> > 
> > As an additional example, we have a way of expressing a user's activity. In
> > certain circumstances, we may want to add time related information:
> > 
> > <activity xmlns='http://jabber.org/protocol/activity'>
> >   <relaxing>
> >     <partying/>
> >     <valid xmlns='http://jabber.org/protocol/something'
> >        from='2002-09-10T20:41:07' 
> >        to='2002-09-10T23:41:07'/> 
> >   </relaxing>
> >   <text xml:lang='en'>My nurse's birthday!</text>
> > </activity>
> Right, for a few Extended Presence features, this would be very useful. I
> will discuss with stpeter, how to best go about it, but your example is
> good candidate.
> I don't believe we should want this for normal availability (using
> <presence/>). You availability should be set by the client, not automagically
> at some time in the future. If I am not there, I am not there.

My understanding of the PIDF/SIMPLE extension (IIRC this was in early
versions of PIDF but seems to have been dropped before it went to RFC)
is that the time periods are hints. The main use case is to integrate
with a calendar -- if my calendar knows I will be in a meeting from 9:00
to 10:30, the calendar could set my show to be "dnd" or my status to be
"in a meeting", and when it updates my presence it could also specify
the expected time period for that presence. Of course, if my meeting
ends early or goes over, then I might manually update my presence since
I doubt that my calendar is smart enough to know that -- unless of course
it also implements JEP-0132. ;-)

The validity syntax looks fine to me (all times UTC, please!). Perhaps a
small JEP on this is in order? I could probably write that one with my
eyes closed. :-)


More information about the Standards mailing list