"When people ask me what we're doing to drive standards, I tell them to go to hell", says James Barry, the new CTO for Jabber, Inc. But there's a twinkle in his voice as he adds the URL: " Hades.jabber.org/ietf". That's where Jabber.org has posted Jabber-rfc, an informational "working document", also known in IETF lingo as an "Internet-draft". RFC more commonly means Request For Comment. IETF is the Internet Engineering Task Force. The latest draft of the document, which runs 80 pages in text format, is dated February 12. In customary open-source fashion, the Jabber folks are exposing the process and inviting participation.
James Barry says this is already a "historical" document, for the simple reason that it's a public source of information to which anybody can easily refer. He also thinks it may be historic in another respect. "Not many open-source projects have made the effort to form standards", he says. "They rely on the code itself to do that. So this is a different approach. It's a great way to legitimize an open-source project. It's a forced rigor. We're documenting what we do to a high degree of accuracy and completeness, to fit the conventions of the IETF."
Jabber's standards are also less a matter of code than of protocol. Here's the abstract:
Jabber is a set of open, XML-based protocols for which there exist multiple implementations. These implementations have been used mainly to provide instant messaging and presence services that are currently deployed on thousands of domains worldwide and are accessed by millions of users daily. Because a standard description of the Jabber protocols is needed to describe this new traffic growing over the Internet, the current document defines the Jabber protocols as they exist today. In addition, this document describes, but does not address, the known deficiencies of the Jabber protocols, since these are being addressed through a variety of standards efforts.
The document is unsparing in its description of deficiencies. For example, "At present the Jabber protocols comply only with a subset of the XML namespace specification and do not offer the full flexibility of XML namespaces. In addition it would be beneficial for the Jabber protocols to enable additional types of availability through a properly namespaced sub-element of the <presence/> data type."
As with all open-source efforts, what needs to be done matters more than what's been done already.
Needless to say, James Barry and other members of the Jabber development community want the document to recruit development help. And since there's a lot of overlap between Jabber and Linux development, we're eager to hear more about the subject from Linux Journal readers as well. Here are three questions that quickly come to mind:
Should innovative open-source projects even bother with the standards process? (Others, such as Apache, don't.)
Does open source in some ways replace the standards process or render it irrelevant?
If not, are there better ways to participate?
Doc Searls is Senior Editor of Linux Journal. He is also a member of the Jabber Inc. Open Source Advisory Board.
Doc Searls is Senior Editor of Linux Journal
Special Reports: DevOps
Have projects in development that need help? Have a great development operation in place that can ALWAYS be better? Regardless of where you are in your DevOps process, Linux Journal can help!
With deep focus on Collaborative Development, Continuous Testing and Release & Deployment, we offer here the DEFINITIVE DevOps for Dummies, a mobile Application Development Primer, advice & help from the experts, plus a host of other books, videos, podcasts and more. All free with a quick, one-time registration. Start browsing now...
- Non-Linux FOSS: Code Your Way To Victory!
- Vagrant Simplified
- Disney's Linux Light Bulbs (Not a "Luxo Jr." Reboot)
- Libreboot on an X60, Part I: the Setup
- Dealing with Boundary Issues
- System Status as SMS Text Messages
- Bluetooth Hacks
- New Products
- October 2015 Issue of Linux Journal: Raspberry Pi
- Linux and the Internet of Things