jabberfoundation at ralphm.ik.nu
Fri Aug 18 04:25:13 CDT 2006
On Thu, Aug 17, 2006 at 11:50:53AM -0600, Peter Saint-Andre wrote:
> I think it may be time to change our protocol branding to XMPP.
I would be fine with naming our protocol extensions XMPP Extensions and
using XMPP exclusively for anything protocol related and changing our
documents and communications on this point.
However, at least currently, our JEP series describe more than only
protocols. Also, the name Jabber Enhancement Proposal describes exactly
the intent of each document: enhancing Jabber. This could be through
XMPP Extensions, but also best practices and organisational stuff.
For example, our JEP-0060 at the top says:
This document defines a publish-subscribe protocol for use on
I would propose to change that into:
This document defines a publish-subscribe XMPP Extension.
I don't see any value in changing the name of these documents or create
a new series with just the current standards and historic track
documents and leaving gaps in the numbering for easier reference.
I could imagine having a series of blessed XMPP Extensions much like the
STD series of the IETF that are basically active standards track JEPs.
Naming the council XMPP Council would be ok with me, as it only decides
on XMPP Extensions.
I also want to note that XEP is the name of an XSL FO rendering engine,
that also has extensions.
More information about the Members