[Standards-JIG] Re: Recommended additions to JEP-130 (Waiting Lists)

Peter Saint-Andre stpeter at jabber.org
Fri Sep 3 19:09:36 UTC 2004


In article <8D96EDA0AC04D31197B400A0C96C148009524033 at corp.webb.net>,
 Craig Kaes <CKaes at jabber.com> wrote:

> Recommended change:
> <iq type='set'
>     to='waitlist.service-provider.com'
>     id='waitinglist1'>
>   <query xmlns='http://jabber.org/protocol/waitinglist'>
>     <item>
>       <uri scheme='tel'>contact-number</uri>
>       <name>Mr. Morton</name>
>     </item>
>   </query>
> </iq>
> 
> Notde the addition of the name element that is now a child of item.
> Further, we should agree on a limit to the length of the text to allow for
> efficient database storage.  Shall we allow, say, 1K of normalized cdata?

This seems good to me.
 
> Lastly, the service can send a notification similar to the successful
> notification (i.e. in a message) that the URI cannot be located.  Something
> like:
> 
> <message
>     type='headline'
>     from='waitlist.service-provider.com'
>     to='user at service-provider.com'>
>   <body>This message contains a waiting list item.</body>
>   <waitlist xmlns='http://jabber.org/protocol/waitinglist'>
>     <item id='12345' type='error'>
>       <uri scheme='tel'>contact-number</uri>
>     </item>
>     <error code='500' type='cancel'>
>         <remote-server-not-found
> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
>     </error>
>   </waitlist>
> </message>

I think this is the best of the three proposed approaches.
 
> Other nits -- the error codes need updating 

Easy enough.

> and I think recommending a
> type='headline' on the notifications is a big mistake.  I've said that I
> want to be notified when this user is added; why wouldn't I want
> notification if I'm offline when the user finally joins?  Seems strange.

I'll make this a MAY.

Look for a revised version soon.

Peter




More information about the Standards mailing list