From b15976ac729fc1feba987d6c00cf0acbe3ba334c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 1 Dec 2006 18:25:38 +0000 Subject: [PATCH] RFC 4622 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@244 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0081.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0081.xml b/xep-0081.xml index 0cb0ec22..738390b8 100644 --- a/xep-0081.xml +++ b/xep-0081.xml @@ -58,7 +58,7 @@ -

The value of a URI scheme (see &rfc3986;) for Jabber/XMPP communications has long been recognized within the Jabber community, and such a scheme has been formally defined in &xmppuri; as a way of identifying entities that adhere to &xmppcore; or its antecedents. Unfortunately, URI schemes are slow to be accepted on the Internet, such that it might be years (if ever) before widely deployed software such as web browsers will support addresses of the form <xmpp:user@domain>.

+

The value of a URI scheme (see &rfc3986;) for Jabber/XMPP communications has long been recognized within the Jabber community, and such a scheme has been formally defined in &rfc4622; as a way of identifying entities that adhere to &xmppcore; or its antecedents. Unfortunately, URI schemes are slow to be accepted on the Internet, such that it might be years (if ever) before widely deployed software such as web browsers will support addresses of the form <xmpp:user@domain>.

Thankfully, it is not necessary for the large existing base of deployed software to support the xmpp: URI scheme in order to integrate Jabber/XMPP support. A well-accepted alternative approach See, for instance, <http://www.mozilla.org/docs/web-developer/mimetypes.html> for information about MIME support in the Mozilla family of web browsers. is to define a MIME type (in accordance with &rfc2045;) and then reconfigure the relevant server and client software to correctly handle the new MIME type.