From 909f9cf9b640be482c9c44631a1c63d7967fd519 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 13 Apr 2009 14:58:53 +0000 Subject: [PATCH] text tweak git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3041 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0134.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0134.xml b/xep-0134.xml index 38cecec2..aef6139d 100644 --- a/xep-0134.xml +++ b/xep-0134.xml @@ -51,7 +51,7 @@ -

The Extensible Messaging and Presence Protocol (XMPP) provides a solid, flexible foundation for a wide variety of applications on top of XMPP's core XML streaming technology. With the advancement of &xmppcore; and &xmppim; within the Internet Standards Process, interest in building XMPP-based applications and extensions has accelerated even further. Unfortunately, not everyone who wants to build public or private XMPP extensions is familiar with the key design criteria that motivated the original developers of the Jabber technologies or that guide successful XMPP-based protocol design today. Thus there is value in attempting to translate the often-implicit knowledge held by long-time Jabber developers and protocol designers into more explicit policies and principles to which others can adhere. For more general insights into Internet protocol design, see &rfc3117;. The end result of explicating "The Jabber Way" will hopefully be a wider and deeper understanding of good protocol design practices within the Jabber/XMPP community.

+

The Extensible Messaging and Presence Protocol (XMPP) provides a solid, flexible foundation for a wide variety of applications on top of XMPP's core XML streaming technology. With the advancement of &xmppcore; and &xmppim; within the Internet Standards Process, interest in building XMPP-based applications and extensions has accelerated even further. Unfortunately, not everyone who wants to build public or private XMPP extensions is familiar with the key design criteria that motivated the original developers of the Jabber technologies or that guide successful XMPP-based protocol design today. Thus there is value in attempting to translate the often-implicit knowledge held by long-time Jabber developers and protocol designers into more explicit policies and principles to which others can adhere. (For more general insights into Internet protocol design, see &rfc3117;.) The end result of explicating "The Jabber Way" will hopefully be a wider and deeper understanding of good protocol design practices within the Jabber/XMPP community.