[Foundation] JSF == Jabber Standards Foundation?

Matt Tucker matt at jivesoftware.com
Thu May 22 18:19:56 CDT 2003


> Jabber is to XMPP as Web is to HTTP.
> Therefore JSF is to the IETF's XMPP WG as W3C is to the IETF's HTTP WG.

I can understand why this is a tempting analogy, but I believe it to be 
a false one.

  1) The web is the tangible manifestation of the use of the HTTP 
protocol. XMPP and Jabber currently both mean the same thing -- a 
protocol. Try out these sentances:

   a) "I found a great deal on a new car on the web" and "I found a 
great deal on a new car on the HTTP"
   b) "Jabber is a great instant messaging protocol" and "XMPP is a 
great instant messaging protocol"

Notice the difference? This is essentially the "confusion" point 
mentioned in previous emails.

  2) Web and HTTP are both generic terms not associated with any 
company. On the other hand, Jabber is the name of the company, which is 
a direct impediment to the XMPP standard's adoption as long as we refer 
to it as Jabber.

> Right now we seem stuck in IM because that's what we're still developing
> to feature-completeness. Personally I can't wait to get beyond that so
> we can define Jabber Calendaring, Jabber Whiteboarding, and many other
> real-time applications.

Yep, this is all exciting stuff. However, I don't think it has much 
relevance to the current debate. We need to:

  * Be focused enough in the short term to get XMPP widely adopted as an 
IM protocol. Otherwise there is no oppurtunity for the XMPP protcol to 
be adopted for other uses.
  * Realize that the term "Jabber" will never be commercially viable to 
standards implementors.


More information about the Members mailing list