[Standards] [xmppwg] encapsulating NodeIDs in XMPP URIs

Peter Saint-Andre stpeter at stpeter.im
Thu Feb 7 16:04:44 UTC 2008

Ralph Meijer wrote:
> On Wed, 2007-12-12 at 09:37 -0700, Peter Saint-Andre wrote:
>> [..]
>> So if there is no node identifier involved, are you suggesting that we
>> would do (2) instead of (1) below?
>> 1. xmpp:ralphm at ik.nu
>> 2. xmpp:ralphm at ik.nu?
>> How do we know that the query type is indeed empty? Do we need to do (3)
>> instead?
>> 3. xmpp:ralphm at ik.nu?;
> Easy, there is no URI query component in 1). I've always said that
> applications that want to deference an XMPP URI like 1), should do
> Service Discovery on the entity's JID that is identified by the URI, and
> present the user possible actions based on that.
> For example, you can have a URI like <xmpp:jdev at conference.jabber.org>.
>>From the URI alone, the application cannot know if this is a user's IM
> account or a MUC room. Depending on the disco identity, an application
> can present the action "open a chat to this user", or "add this user to
> my roster", or "add this room to my roster" or "join this room".

Agreed. I think we say that in XEP-0147 or RFC 4622, so do you propose
any modifications to those documents?


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080207/74797468/attachment.bin>

More information about the Standards mailing list