stpeter at jabber.org
Fri Aug 18 10:43:06 CDT 2006
Ralph Meijer wrote:
> 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.
Yes, this is all about protocols.
> 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.
Yes, those procedural documents might belong somewhere else, though I
think it's cleaner to have everything in one place -- e.g., RFCs also
define procedural and organizational items.
> For example, our JEP-0060 at the top says:
> This document defines a publish-subscribe protocol for use on
> Jabber/XMPP networks.
> I would propose to change that into:
> This document defines a publish-subscribe XMPP Extension.
Oh yes, over time I've been cleaning up some of that kind of language,
but more remains to be done.
> 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.
Agreed, one series only please.
> 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.
Those are Final XEPs, no? Personally I've always found the IETF system
confusing (STD, BCP, etc.).
> Naming the council XMPP Council would be ok with me, as it only decides
> on XMPP Extensions.
Sure, XMPP Council, XMPP Registrar, XEP Editor, etc.
> I also want to note that XEP is the name of an XSL FO rendering engine,
> that also has extensions.
And JSF is "Joint Strike Fighter"... :-)
Probably there are no TLAs that won't conflict with something someone
else is using.
Jabber Software Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/members/attachments/20060818/8cc6ada9/smime.bin
More information about the Members