moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

XMPP URI reference

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1783 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-04-18 16:51:03 +00:00
parent 02d05fea73
commit b6f8be2206
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-0032.xml
View File

@ -15,7 +15,7 @@
<sig>Standards</sig>
<dependencies>None</dependencies>
<supersedes>None</supersedes>
<supersededby><spec>RFC 4622</spec></supersededby>
<supersededby><spec>RFC 5122</spec></supersededby>
&stpeter;
&pgmillard;
<revision>
@ -44,7 +44,7 @@
</revision>
</header>
<section1 topic='Introduction'>
<p><em>Note: This document has been superseded by &rfc4622;.</em></p>
<p><em>Note: This document has been superseded by &rfc5122;.</em></p>
<p>It is widely acknowledged that it would be good to be able to express a Jabber Identifier (JID) (see &xep0029;) as a Uniform Resource Identifier (see &rfc3986;). In addition, there would be value in being able to interact with a JID through a URI scheme (e.g., by sending a message or a presence update).</p>
<p>Although XMPP enables a wide range of functionality, the authors propose that a Jabber URI scheme needs to support only a limited subset of the possible Jabber functionality. In particular, we see the following as core functions that need to be supported:</p>
<ul>