This JEP provides information intended to assist authors of Jabber Enhancement Proposals.
NOTICE: This JEP is currently within Last Call or under consideration by the Jabber Council for advancement to the next stage in the JSF standards process. For further details, visit <http://www.jabber.org/council/queue.php>.
Last Updated: 2004-10-22
JIG: Standards JIG
Approving Body: Jabber Council
Superseded By: None
Short Name: N/A
This Jabber Enhancement Proposal is copyright 1999 - 2004 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy <http://www.jabber.org/jsf/ipr-policy.php>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <http://www.opencontent.org/openpub/>).
The preferred venue for discussion of this document is the Standards-JIG discussion list: <http://mail.jabber.org/mailman/listinfo/standards-jig>.
The Jabber Software Foundation (JSF)  receives a significant number of proposals for defining extensions to the core XMPP protocols specified in XMPP Core . However, it is not always clear to authors how to best structure a proposal in order for it to be accepted as a Jabber Enhancement Proposal and then advance through the JSF's standards process. Therefore, this JEP provides guidelines that are intended to help authors write better JEPs.
These guidelines assume that the reader is familiar with the JEP series of documents and the processes for handling them within the JSF, as defined in Jabber Enhancement Proposals .
The prospective author is strongly encouraged to complete some research before submitting a proposal for consideration as a JEP. In particular, the author should do the following:
After completing this research, the prospective author may conclude that a new protocol extension is needed. If so, the author is strongly advised to do the following:
The process for submitting a JEP is straightforward:
The JEP XML format is substantially similar to a reduced set of XHTML. This is intentional: it makes authoring JEPs easier. In fact, if you use the JEP template file with its associated XSLT stylesheet, you should be able to view your proposal in most modern web browsers (see below). The following subsections explain how to get started with JEP authoring and describe the XML format used for JEPs (see the jep.xsd or jep.dtd file for a formal description).
The best way to start working on your proposal is to retrieve all of the existing JEPs and associated stylesheets from source control. These files are stored using the CVS system, in a CVS module labelled 'jeps' at the jabberstudio.org CVS repository. Instructions for accessing these files are provided at <http://www.jabberstudio.org/cvs.php>. The document structure is formally defined by both a DTD and an XML schema, but you do not need to understand the formal descriptions in order to author a JEP. In addition, a handy template file is included under the 'templates/' directory in the 'jeps' module, providing a quick starting point for JEP authoring.
To create your proposal, do a CVS checkout of the 'jeps' module, create a new directory (e.g., 'tmp/') for your JEP within the existing 'jeps/' directory, copy the template file from the 'template/' directory to your new directory, and start editing the file using either a basic text editor or a specialized XML editing application such as XML Spy or XMLmind.
Even if you use a basic text editor, you should be able to view your JEP in most modern web browsers as an XML file as long as you have jep.xsl and jep.dtd in the 'jeps/' directory (i.e., the parent of the directory for your specific JEP). Because of inconsistencies in browser XSLT implementations, certain formatting (e.g., table layouts and the numbering of tables, examples, and footnotes) may not be perfect. Don't panic; it will look fine in the HTML output produced by the JEP Editor. If your XML file doesn't render at all (i.e., it's just one big text blob), you are using the wrong browser. If you see only the bare outline generated by jep.xsl but none of your text, you have an error in your XML. You can check your XML syntax at xml.com .
To programatically convert your XML file into HTML, we recommend using Daniel Veillard's xsltproc program, which will give you helpful error messages regarding XML syntax problems. However, the JEP Editor will do the final rendering of XML into HTML as well as posting of your HTML file to the JSF website, so you do not need to generate HTML files for submission to the JEP Editor (in fact, the JEP Editor requires that you submit your proposal in the JEP XML format, not HTML).
Finally, the jep.ent file contains convenient "external entities" that provide shortcuts for including references to JEPs, RFCs, and other common strings. Unfortunately, most browsers do not correctly process external entities, so you cannot include entities from jep.ent if you need to view your XML source file in a browser. However, the JEP Editor reserves the right to convert your markup to external entities, since it makes his life easier. Also, please do not add items to the jep.ent file; instead, ask the JEP Editor to add them for you.
This section describes the metadata elements contained in the <header/> element of a JEP file (see below for the file contents).
The XML character data of the <title/> element is the title of your JEP. Choose a descriptive title that is less than five words long. The JEP Editor may change this in consultation with the author.
The XML character data of the <abstract/> element SHOULD be one sentence that captures the essence of your proposal (usually beginning "This JEP defines a protocol that..."). The JEP Editor has been known to modify the abstract so that it accurately describes the proposal.
The XML character data of the <legal/> element MUST be as follows:
This Jabber Enhancement Proposal is copyright 1999 - 2004 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy (http://jabber.org/jsf/ipr-policy.php). This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Your JEP number will be assigned by the JEP Editor; thus you can just make the XML character data of the <number/> element "xxxx".
The XML character data of the <status/> element SHOULD be "Experimental" since all JEPs start out as Experimental.
The XML character data of the <type/> element SHOULD be either "Standards Track" or "Informational" (there are also Historical and Procedural JEPs, but these are uncommon and usually written by the JEP Editor). A Standards Track JEP is basically any JEP that defines a protocol to be used in the Jabber community. An Informational JEP defines best practices or a usage profile related to an existing protocol (e.g., Invisibility ).
The XML character data of the <approver/> element SHOULD be "Council".
The <dependencies/> element is used to specify JEPs, RFCs, and other specifications on which your proposal depends in a normative fashion (i.e., specifications that MUST or SHOULD be implemented in order to implement your proposed protocol). Each specification MUST be identified by a distinct <spec/> child element (see existing JEPs for clues regarding document identifiers, or consult with the JEP Editor).
The <supersedes/>, <supersededby/>, <shortname/>, and <schemaloc/> elements are for use by the JEP Editor; however, if your JEP supersedes an existing JEP, feel free to include a <spec/> child element specifying the document identifier (e.g., JEP-0093) for the protocol that is being superseded.
Include one <author/> element for each co-author. Note well that the <firstname/>, <surname/>, <email/>, and <jid/> elements are all REQUIRED per JEP-0001.
Include one <revision/> element for each revision of your JEP. The XML character data of the <version/> element SHOULD be "0.0.1" for your initial submission to the JEP Editor, and the <remark/> SHOULD be "Initial version."; for each revision, you will include another <revision/> element (place it before the existing <revision/> elements) and iterate the <version/> element (e.g., "0.2" after "0.1"). The format for the <date/> element is yyyy-mm-dd. Please do not include the characters ' or " in your revision remarks.
Aside from the metadata in the JEP <header/> element (see above), a JEP file is a series of sections, arranged in a hierarchy (<section1/> is a top-level section, within which you can nest <section2/> sections, and so on down to <section4/>). The title of a section is captured in the 'topic' attribute. You should also include an 'anchor' element so that you can link to page fragments from within your JEP. The allowable elements within a section element probably look familiar: <p/> for paragraphs, <ol/> and <ul/> for ordered and unordered lists, and so on.
The <example/> and <code/> elements are used to show protocol snippets; the <example/> element SHOULD possess a 'caption' attribute that describes the example, whereas the <code/> element does not. Define an XML CDATA section within both of these elements so that you do not need to escape the '<' and '>' characters in your sample XML stanzas, since this makes life much easier for author and editor alike (see the markup in existing JEPs).
The <p/> and <li/> elements can also contain more markup that is familiar from HTML, such as the <img/> element. Note that hyperlinks are of the form <link url='foo'>bar</link> rather than <a href='foo'>bar</a>; the reasons for this are lost in the mists of time and it is too late to change it now, so you'll just have to adjust. If needed, you can also use inline structural and presentational markup such as <em/>, <strong/>, <tt/>, <cite/>, and <span/> within the <p/> and <li/> elements.
You may also include tables (these are helpful for listing error codes and such). The <table/> element SHOULD possess a 'caption' attribute that describes the table's contents. Standard HTML table structure applies (<tr/> defines a row, which contains <th/> elements for header rows and <td/> elements for data rows), and the 'colspan' and 'rowspan' attributes are also available if you need them. Table presentation (such as cellpadding and cellspacing) is handled by the XSLT and CSS stylesheets.
In fact, the jep.xsl file performs all sorts of magic in converting your XML file into HTML, including creation of the front matter, table of contents, section numbering, notes, and revision history. Feel free to submit patches for this file, but do not commit your modified version to CVS.
Most JEPs will have most of the following sections, usually in something like the order shown. Other sections may be appropriate (e.g., XHTML-IM  has a section for W3C Considerations). Use your best judgment regarding the sections you need in order to make your argument, or consult with the JEP Editor regarding your needs.
The introduction to a JEP is quite important since it provides the rationale for considering the proposal. In particular, the introduction SHOULD include information such as the following:
Every JEP SHOULD include a section describing the requirements being addressed by the JEP. This information is critically important, because it clearly defines the scope of the proposal as well as any relevant constraints on the protocol design.
If your JEP uses terms that may not be familiar to the reader, please define them in a terminology section.
It is recommended that JEP authors structure their proposals according to the use cases that the proposal will address.  We have found that use cases force JEP authors to focus on functionality rather than "protocol for the sake of protocol". It is also helpful to sort use cases by actor, as is done in Multi-User Chat , for example. Include one subsection for each use case.
When writing use cases and the associated protocols, make sure to:
We just said so, but we will repeat ourselves: include lots of protocol examples. Examples help not only implementors but also those who will review your proposal in the Standards JIG and Jabber Council. You get extra credit with the JEP Editor if you follow Jabber tradition by using characters and situations from the plays of Shakespeare:
<message firstname.lastname@example.org/balcony' email@example.com/garden' type='chat'> <body>Wherefore art thou, Romeo?</body> </message>
If your proposal defines a number of error and status codes (as is done in JEP-0045), it is a good idea to include a table of all the codes defined in your document.
You may want to include a section describing various business rules (essentially, a variety of MUSTs, SHOULDs, and MAYs regarding application behavior). This is not required but can be helpful to implementors.
You may want to include a section devoted to implementation notes. Again, this is not required but can be helpful to implementors.
If there are any internationalization or localization issues related to your proposal (e.g., whether to include the 'xml:lang' attribute), define them in this optional section.
Your proposal MUST include a section entitled "Security Considerations". Even if there are no security features or concerns related to your proposal, you MUST note that fact. For helpful guidelines, refer to RFC 3552 .
This section is REQUIRED. The IANA is the Internet Assigned Numbers Authority, the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. Most proposals do not require interaction with the IANA, in which case the text of this section SHOULD read "This JEP requires no interaction with the Internet Assigned Numbers Authority (IANA)." If your proposal requires interaction with the IANA, discuss the matter with the JEP Editor. Do not contact the IANA on your own!
This section is REQUIRED. The Jabber Registrar maintains a list of reserved Jabber protocol namespaces as well as registries of parameters used in the context of protocols approved by the Jabber Software Foundation. If your proposal does not require interaction with the Jabber Registrar, the text of this section SHOULD read "No namespaces or parameters need to be registered with the Jabber Registrar as a result of this JEP." Refer to Draft or Final JEPs for appropriate text in other cases, or consult with the JEP Editor.
An XML Schema is required in order for a protocol JEP to be approved by the Jabber Council. The JEP Editor can assist you in defining an XML Schema for the protocol you are proposing.
Some JEPs end with a section thanking non-authors who have made significant contributions to the specification; if that is true of your JEP, feel free to include this section.
Note: JEP authors can consider this a kind of "Implementation Guidelines". :-)
JEPs are written in English. It is not expected that you will be a fine prose writer, but try to write in a clear, easily-understood fashion. The JEP Editor will correct any errors of grammar, spelling , punctuation, and usage he may find in your proposal, but may not do so until your proposal is in the Jabber Council's queue for consideration. In addition, the JEP Editor reserves the right to improve phrases that are unclear or infelicitous, move sections around, modify examples to use Shakespearean characters, and otherwise improve the argument and logical flow of your proposal (naturally, without changing the meaning).
The following styleguide is provided to supplement the standard English styleguides, such as The Elements of Style and the Chicago Manual of Style; please refer to those resources for information about basic English usage and to this styleguide for JEP-specific guidelines.
When talking about an attribute by name, refer to it in single quotes. Example: the 'to' attribute.
When talking about an attribute value, refer to it in double quotes. Example: the value of the 'subscription' attribute is "both".
Elements possess attributes and contain character data and/or child elements; do not confuse these terms.
In examples, use single quotes rather than double quotes; they are more readable.
To show the hierarchy of XML elements, indent two spaces for every level.
If an element possesses a large number of attributes, include a line break before each attribute and indent them by four spaces or so that the attributes are vertically aligned for readability.
If the XML character data of an element is long, include line breaks and indent by two spaces.
Examples are the major source of right-scrolling in our HTML output files. Right-scrolling is evil. Adjust your example layouts accordingly (line widths should be no more than 110 characters or so).
<iq firstname.lastname@example.org' id='config1' email@example.com/desktop' type='result'> <query xmlns='http://jabber.org/protocol/muc#owner'> <x xmlns='jabber:x:data' type='form'> <title>Configuration for "darkcave" Room</title> <instructions> Please coomplete this form to make changes to the configuration of your room; to add room owners and administrators, use the appropriate room commands rather than this form. </instructions> <field type='hidden' var='FORM_TYPE'> <value>http://jabber.org/protocol/muc#owner</value> </field> </query> </iq>
Conformance terms (e.g,, "MUST" and "SHOULD") are specified in RFC 2119. Use them. When such terms are not in ALL CAPS, the special conformance sense does not apply (this should be obvious but may not be to all authors).
When talking about an element by name, refer to it as an empty XML element. Example: the <query/> element.
The top-level <message/>, <presence/>, and <iq/> elements are actually XML stanzas (see XMPP Core); refer to them as such.
Elements possess attributes and contain character data and/or child elements; do not confuse these terms.
Do not use the term "tag" when you mean "element".
Note: There are shortcuts for stanza names and some common element names in the jep.ent file.
When talking about an error condition, use the XML element names defined in XMPP Core rather than the old HTTP-style code numbers. Example: the <feature-not-implemented/> error.
Note: There are shortcuts for the stanza errors in the jep.ent file.
When talking about a namespace by name, refer to it in single quotes. Example: the 'jabber:iq:roster' namespace.
An element or attribute is qualified by (rather than "scoped by" or "in") a particular namespace.
For precision, the JSF follows IETF usage by placing all punctuation outside the quotation marks unless one is quoting text that includes the punctuation. Example: the port used for Jabber client communications is "5222".
1. The Jabber Software Foundation (JSF) is an independent, non-profit organization that develops open application protocols on top of the IETF's Extensible Messaging and Presence Protocol (XMPP). For further information, see <http://www.jabber.org/jsf/>.
2. RFC 3920: Extensible Messaging and Presence Protocol (XMPP): Core <http://www.ietf.org/rfc/rfc3920.txt>.
3. JEP-0001: Jabber Enhancement Proposals <http://www.jabber.org/jeps/jep-0001.html>.
4. The Jabber Council is a technical steering committee, authorized by the JSF Board of Directors and elected by JSF members, that approves of new Jabber protocols and oversees the JSF's standards process. For further information, see <http://www.jabber.org/council/>.
5. The Internet Engineering Task Force is the principal body engaged in the development of new Internet standard specifications, best known for its work on standards such as HTTP and SMTP. For further information, see <http://www.ietf.org/>.
6. The World Wide Web Consortium defines data formats and markup languages (such as HTML and XML) for use over the Internet. For further information, see <http://www.w3.org/>.
7. The Standards JIG is a standing Jabber Interest Group devoted to discussion of Jabber Enhancement Proposals. The discussion list of the Standards JIG is the primary venue for discussion of Jabber protocol development, as well as for announcements by the JEP Editor and Jabber Registrar. To subscribe to the list or view the list archives, visit <http://mail.jabber.org/mailman/listinfo/standards-jig/>.
8. JEP-0134: Protocol Design Guidelines <http://www.jabber.org/jeps/jep-0134.html>.
9. The JEP Editor is the individual appointed by the JSF Board of Directors to handle protocol submissions and provide day-to-day management of the JSF's standards process. For further information, see <http://www.jabber.org/jeps/editor.php>.
10. The JSF IPR Policy defines the Jabber Software Foundation's official policy regarding intellectual property rights (IPR) as they pertain to Jabber Enhancement Proposals (JEPs). For further information, see <http://www.jabber.org/jsf/ipr-policy.php>.
12. JEP-0126: Invisibility <http://www.jabber.org/jeps/jep-0126.html>.
13. JEP-0071: XHTML-IM <http://www.jabber.org/jeps/jep-0071.html>.
14. A good introduction to use cases may be found at <http://www.pols.co.uk/usecasezone/>.
15. JEP-0045: Multi-User Chat <http://www.jabber.org/jeps/jep-0045.html>.
16. RFC 3552: Guidelines for Writing RFC Text on Security Considerations <http://www.ietf.org/rfc/rfc3552.txt>.
17. With all due respect to authors in other parts of the world, JEPs follow American spelling conventions; thus "authorise" will be changed to "authorize" and such.