[Members] s/JEP/XEP/g

Peter Saint-Andre stpeter at jabber.org
Mon Aug 21 11:42:27 CDT 2006

Edwin Mons wrote:
> Ian Paterson wrote:
>> Ralph wrote:
>>> I have not seen convincing reasons to rename them into, for example,
>>> XEPs.
>> XEP is far more descriptive. These protocols extend a protocol we've
>> all agreed to call XMPP.
>> If we use XEP then we won't have to explain to the newbies why the
>> authorittive extensions are called JEPs not XEPs.
>>> I think it is important to make sure that people who only come in
>>> contact with the term XMPP regard the JSF as /the/ authoritive entity
>>> for defining XMPP protocol extensions
>> Yes. Changing the name to XEP can only help us to 'position' our
>> protocols in that way.
>> And by claiming the XEP name (and the associated numbering sequence)
>> for its protocols, the JSF will disuade other corporations or
>> organisations from using it in the future.
> Just my two cents: I tend to agree to the "Web is to HTTP as Jabber is
> to XMPP" analogy.  Jabber is just too nice a name (and too well known)
> to discard just like that.

I never said anything about discarding the JABBER name, only changing
the name of our protocol specification series.

> Changing the name JEP to XEP wouldn't help anybody, I think.  Yes, you
> have the link between XMPP and the enhancement in the name, but why
> should that be relevant?

Well, you would not believe the number of people who have poked me about
the fact that JEP stands for Jabber Enhancement Proposal -- they think
that a JEP is not something they need to care about because:

1. It's about Jabber, not XMPP

2. It's just an enhancement, not an extension

3. It's just a proposal, not a standard

I realize that people who think that way are myopic. But we have to deal
with them and their way of thinking. If we use the phrase "XMPP
Extension Protocol" then they will be more willing to implement and
deploy the technologies we develop. And that's a good thing.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/members/attachments/20060821/66c8f5f9/smime-0001.bin

More information about the Members mailing list