moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 02:32:18 -05:00
Code Issues Releases Wiki Activity

corrected examples

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3975 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2010-02-22 04:40:24 +00:00
parent 9b8f36145c
commit d08bc7e9c8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0165.xml
View File

@ -137,11 +137,11 @@
<section2 topic='Subscription Requests' anchor='rec-subscriptions'> <section2 topic='Subscription Requests' anchor='rec-subscriptions'>
<p>We have seen that, at a minimum, three names or address types are needed to provide a petname system for XMPP: a JID, a nickname, and a handle (preferably strengthened by inclusion of a fingerprint derived from a key). However, at present a subscription request contains only the JID of the sender:</p> <p>We have seen that, at a minimum, three names or address types are needed to provide a petname system for XMPP: a JID, a nickname, and a handle (preferably strengthened by inclusion of a fingerprint derived from a key). However, at present a subscription request contains only the JID of the sender:</p>
<example caption='A Basic Subscription Request'><![CDATA[ <example caption='A Basic Subscription Request'><![CDATA[
<presence from='stpeter@jabber.org to='MaineBoy@jabber.org' type='subscribe'/> <presence from='stpeter@jabber.org' to='MaineBoy@jabber.org' type='subscribe'/>
]]></example> ]]></example>
<p>Naturally, based on the JID, it is possible to pull information about the sender from a persistent data store such as an LDAP database, &xep0054; node, or future profile system (see &xep0154;). However, to speed interactions, this document recommends that when a client sends a subscription request, it SHOULD include the preferred nickname of the sender (encapsulated via the format specified in <cite>XEP-0172</cite>) and the sender's key or keys.</p> <p>Naturally, based on the JID, it is possible to pull information about the sender from a persistent data store such as an LDAP database, &xep0054; node, or future profile system (see &xep0154;). However, to speed interactions, this document recommends that when a client sends a subscription request, it SHOULD include the preferred nickname of the sender (encapsulated via the format specified in <cite>XEP-0172</cite>) and the sender's key or keys.</p>
<example caption='Subscription Request With Nickname and Key'><![CDATA[ <example caption='Subscription Request With Nickname and Key'><![CDATA[
<presence from='stpeter@jabber.org to='MaineBoy@jabber.org' type='subscribe'> <presence from='stpeter@jabber.org' to='MaineBoy@jabber.org' type='subscribe'>
<nick xmlns='http://jabber.org/protocol/nick'>psa</nick> <nick xmlns='http://jabber.org/protocol/nick'>psa</nick>
<KeyInfo xmlns='http://www.w3.org/2000/09/xmldsig#'> <KeyInfo xmlns='http://www.w3.org/2000/09/xmldsig#'>
<KeyName>stpeterRSAkey1</KeyName> <KeyName>stpeterRSAkey1</KeyName>