diff --git a/xep-0023.xml b/xep-0023.xml index a8618d43..1f7d6136 100644 --- a/xep-0023.xml +++ b/xep-0023.xml @@ -7,7 +7,7 @@
Message Expiration - This JEP documents an historical protocol that was used to specify expiration dates for messages; this protocol has been deprecated in favor of JEP-0079: Advanced Message Processing. + This specification documents an historical protocol that was used to specify expiration dates for messages; this protocol has been deprecated in favor of JEP-0079: Advanced Message Processing. &LEGALNOTICE; 0023 Deprecated diff --git a/xep-0025.xml b/xep-0025.xml index 0082ebf0..628c3ea0 100644 --- a/xep-0025.xml +++ b/xep-0025.xml @@ -62,7 +62,7 @@

Note Well: This protocol specified in this document has been superseded by the protocol specified in &jep0124;.

- This JEP documents a method to allow Jabber clients to access Jabber + This specification documents a method to allow Jabber clients to access Jabber servers from behind existing firewalls. Although several similar methods have been proposed, this approach should work through all known firewall configurations which allow outbound HTTP access. diff --git a/xep-0027.xml b/xep-0027.xml index 78199105..edd3203a 100644 --- a/xep-0027.xml +++ b/xep-0027.xml @@ -60,7 +60,7 @@

-

The Jabber community has long acknowledged the need for privacy and security features in a well-rounded instant messaging system. Unfortunately, finding a consensus solution to the problem of end-to-end encryption during the community's younger days was not easy. Eventually, early contributors created a quick solution using OpenPGP. This JEP documents the OpenPGP solution as it is used today, so that others may interoperate with clients that support it. This JEP is not intended to present a standard, because more complete solutions are being investigated.

+

The Jabber community has long acknowledged the need for privacy and security features in a well-rounded instant messaging system. Unfortunately, finding a consensus solution to the problem of end-to-end encryption during the community's younger days was not easy. Eventually, early contributors created a quick solution using OpenPGP. This specification documents the OpenPGP solution as it is used today, so that others may interoperate with clients that support it. This JEP is not intended to present a standard, because more complete solutions are being investigated.

All operations described here are done with standard OpenPGP software such as GnuPG. All program output is US-ASCII armored output with the headers removed. This allows for easy transportation of the program output directly in the XML. All keys are exchanged using OpenPGP key servers, and usually are retrieved when a signed &PRESENCE; stanza is received (key retrieval does not happen in-band).

 diff --git a/xep-0048.xml b/xep-0048.xml index 8076453d..51856e87 100644 --- a/xep-0048.xml +++ b/xep-0048.xml @@ -7,7 +7,7 @@
Bookmark Storage - This JEP documents a protocol for the storage of bookmarks to conference rooms and other entities in a Jabber user's account. + This specification documents a protocol for the storage of bookmarks to conference rooms and other entities in a Jabber user's account. &LEGALNOTICE; 0048 Active diff --git a/xep-0049.xml b/xep-0049.xml index 5d14868e..6bfbd0c1 100644 --- a/xep-0049.xml +++ b/xep-0049.xml @@ -7,7 +7,7 @@
Private XML Storage - This JEP provides canonical documentation of the 'jabber:iq:private' namespace currently in common usage. + This specification provides canonical documentation of the 'jabber:iq:private' namespace currently in common usage. &LEGALNOTICE; 0049 Active @@ -80,7 +80,7 @@
-

The 'jabber:iq:private' namespace has previously been documented in the Jabber Programmers Guide, but not in a canonical form such as the Internet-Drafts or a JEP. This JEP documents the existing usage of jabber:iq:private.

+

The 'jabber:iq:private' namespace has previously been documented in the Jabber Programmers Guide, but not in a canonical form such as the Internet-Drafts or a JEP. This specification documents the existing usage of jabber:iq:private.

 diff --git a/xep-0053.xml b/xep-0053.xml index cd871fe7..e5a6b7cc 100644 --- a/xep-0053.xml +++ b/xep-0053.xml @@ -1,13 +1,13 @@ - + %ents; ]> - - + +
- Jabber Registrar - This JEP defines the roles and processes of the Jabber Registrar within the Jabber Software Foundation. + XMPP Registrar + This document defines the roles and processes of the XMPP Registrar within the Jabber Software Foundation. &LEGALNOTICE; 0053 Active @@ -29,13 +29,13 @@ 1.0 2003-03-20 psa - Per a vote of the Jabber Council, advanced status to Active. + Per a vote of the XMPP Council, advanced status to Active. 0.5 2003-01-21 psa - Changed name to Jabber Registrar in response to feedback from the JSF Board of Directors. + Changed name to XMPP Registrar in response to feedback from the JSF Board of Directors. 0.4 @@ -47,7 +47,7 @@ 0.3 2002-11-22 psa - Simplified to reflect discussion in the Jabber Council; in particular, reserved JANA functions to the JEP Editor until there is a perceived need for a more formal governing body. + Simplified to reflect discussion in the XMPP Council; in particular, reserved JANA functions to the XMPP Extensions Editor until there is a perceived need for a more formal governing body. 0.2 @@ -63,24 +63,24 @@
-

As the &JSF; publishes more protocol specifications (see &jep0001;), it becomes necessary to keep better track of the namespaces defined by those specifications as well as the parameters used in the context of the relevant protocols. (Examples of such parameters include the features and options used in &jep0020; and the identities and features used in &jep0030;.) In particular, the common use of protocols published by the JSF requires that namespaces and particular parameter values be assigned uniquely. It is the role of the Jabber Registrar to make those unique assignments and to maintain registries of the currently assigned values. The Jabber Registrar shall also function as a single point of contact between the Jabber community and &IANA;.

+

As the &JSF; publishes more protocol specifications (see &xep0001;), it becomes necessary to keep better track of the namespaces defined by those specifications as well as the parameters used in the context of the relevant protocols. (Examples of such parameters include the features and options used in &xep0020; and the identities and features used in &xep0030;.) In particular, the common use of protocols published by the JSF requires that namespaces and particular parameter values be assigned uniquely. It is the role of the XMPP Registrar to make those unique assignments and to maintain registries of the currently assigned values. The XMPP Registrar shall also function as a single point of contact between the Jabber/XMPP developer community and &IANA;.

 -

Until there is a perceived need for a more formal governing body, the functions of the Jabber Registrar shall be managed by the &EDITOR;. In the future, the &COUNCIL; and/or the &BOARD; may decide to create a more formal panel to oversee the functions of the Jabber Registrar; if they do, this JEP shall be updated to reflect the change.

+

Until there is a perceived need for a more formal governing body, the functions of the XMPP Registrar shall be managed by the &EDITOR;. In the future, the &COUNCIL; and/or the &BOARD; may decide to create a more formal panel to oversee the functions of the XMPP Registrar; if they do, this document shall be updated to reflect the change.

 -

Every Jabber Enhancement Proposal (JEP) must contain a section devoted to "Jabber Registrar Considerations", detailing the namespaces and parameters to be registered with the Jabber Registrar, as well as any new registries to be created as a result of the JEP.

-

The registry additions or creations specified in a JEP shall not take effect until the JEP advances to a status of Draft (Standards-Track JEPs) or Active (Informational and Historical JEPs). Registration of namespaces shall be initiated by the JEP Editor when a JEP advances to Draft or Active and shall not require the involvement of the JEP author. Registration of particular parameters used within a specification shall be initiated by the JEP Editor if specified in the JEP, and may also be initiated by implementers of the JEP after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the Jabber Registrar; if a JEP specifies the creation of a new registry, the JEP author is strongly encouraged to consult with the Jabber Registrar before seeking a Last Call on the JEP.

-

Requests for namespace and parameter assignments must be sent to the Jabber Registrar in accordance with the process specified in the document (usually a JEP) that defines the relevant registry, normally by sending an appropriately formatted email message to <registrar@jabber.org>. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SJIG;. The Registrar shall add registry items at his discretion based on discussion within the Standards JIG if necessary, but shall not unduly restrict registration of parameter values. If a JEP author or implementer thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the Jabber Council.

-

The Jabber Registrar shall maintain registries of assigned namespaces and parameters at <http://www.jabber.org/registrar/> and shall update those registries in a timely fashion. Changes to JSF registries shall be announced on the Standards-JIG mailing list.

+

Every XMPP Extension Protocol specification (XEP) must contain a section devoted to "XMPP Registrar Considerations", detailing the namespaces and parameters to be registered with the XMPP Registrar, as well as any new registries to be created as a result of the XEP.

+

The registry additions or creations specified in an XMPP Extension Protocol specification shall not take effect until the document advances to a status of Draft (Standards-Track XEPs) or Active (Informational and Historical XEPs). Registration of namespaces shall be initiated by the XMPP Extensions Editor when a XEP advances to Draft or Active and shall not require the involvement of the document author. Registration of particular parameters used within a specification shall be initiated by the XMPP Extensions Editor if specified in the XEP, and may also be initiated by implementors of the XMPP Extension Protocol document after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the XMPP Registrar; if a document specifies the creation of a new registry, the author is strongly encouraged to consult with the XMPP Registrar before seeking a Last Call on the XEP.

+

Requests for namespace and parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to <registrar@jabber.org>. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SJIG;. The Registrar shall add registry items at his discretion based on discussion within the Standards JIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementer thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.

+

The XMPP Registrar shall maintain registries of assigned namespaces and parameters at <http://www.xmpp.org/registrar/> and shall update those registries in a timely fashion. Changes to JSF registries shall be announced on the Standards-JIG mailing list.

 -

Security considerations are primarily the responsibility of the protocols in which specific parameters are used. The Jabber Registrar shall respect the security considerations defined in JSF protocol specifications, and shall endeavor to ensure that registered parameter values do not compromise privacy or security in any way.

+

Security considerations are primarily the responsibility of the protocols in which specific parameters are used. The XMPP Registrar shall respect the security considerations defined in JSF protocol specifications, and shall endeavor to ensure that registered parameter values do not compromise privacy or security in any way.

 -

The Jabber Registrar shall be responsible for interacting with the IANA on behalf of the Jabber community. If a JEP requires interaction with the IANA, that fact shall be noted by the JEP author in the JEP and discussed on the Standards-JIG mailing list along with normal discussion of the JEP. The Jabber Registrar shall collaborate with the JEP author to present an appropriate request to the IANA.

+

The XMPP Registrar shall be responsible for interacting with the IANA on behalf of the Jabber Software Foundation and Jabber/XMPP developer community. If an XMPP Extension Protocol document requires interaction with the IANA, that fact shall be noted by the document author and discussed on the Standards-JIG mailing list along with normal discussion of the XEP. The XMPP Registrar shall collaborate with the author to present an appropriate request to the IANA.

 - -

This entire document defines the processes and procedures of the Jabber Registrar.

+ +

This entire document defines the processes and procedures of the XMPP Registrar.

 - + diff --git a/xep-0054.xml b/xep-0054.xml index a652dff5..ec037486 100644 --- a/xep-0054.xml +++ b/xep-0054.xml @@ -7,7 +7,7 @@
vcard-temp - This JEP provides canonical documentation of the vCard-XML format currently in use within the Jabber community. + This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community. &LEGALNOTICE; 0054 Active @@ -46,7 +46,7 @@
-

This JEP documents the vCard-XML format currently in use within the Jabber community. A future JEP will recommend a standards-track protocol to supersede this informational document.

+

This specification documents the vCard-XML format currently in use within the Jabber community. A future JEP will recommend a standards-track protocol to supersede this informational document.

The basic functionality is for a user to store and retrieve an XML representation of his or her vCard using the data storage capabilities native to all existing Jabber server implementations. This is done by by sending an <iq/> of type "set" (storage) or "get" (retrieval) to one's Jabber server containing a <vCard/> child scoped by the 'vcard-temp' namespace, with the <vCard/> element containing the actual vCard-XML elements as defined by the vCard-XML DTD. Other users may then view one's vCard information.

 diff --git a/xep-0055.xml b/xep-0055.xml index 00b3e3ef..697333ae 100644 --- a/xep-0055.xml +++ b/xep-0055.xml @@ -7,7 +7,7 @@
Jabber Search - This JEP provides canonical documentation of the 'jabber:iq:search' namespace currently in use within the Jabber community. + This specification provides canonical documentation of the 'jabber:iq:search' namespace currently in use within the Jabber community. &LEGALNOTICE; 0055 Active @@ -50,7 +50,7 @@
-

This JEP documents a protocol currently used to search information repositories on the Jabber network. To date, the jabber:iq:search protocol has been used mainly to search for people who have registered with user directories (e.g., the "Jabber User Directory" hosted at users.jabber.org). However, the jabber:iq:search protocol is not limited to user directories, and could be used to search other Jabber information repositories (such as chatroom directories) or even to provide a Jabber interface to conventional search engines.

+

This specification documents a protocol currently used to search information repositories on the Jabber network. To date, the jabber:iq:search protocol has been used mainly to search for people who have registered with user directories (e.g., the "Jabber User Directory" hosted at users.jabber.org). However, the jabber:iq:search protocol is not limited to user directories, and could be used to search other Jabber information repositories (such as chatroom directories) or even to provide a Jabber interface to conventional search engines.

The basic functionality is to query an information repository regarding the possible search fields, to send a search query, and to receive search results. Note well that there is currently no mechanism for paging through results or limiting the number of "hits", and that the allowable search fields are limited to those defined in the XML schema; however, extensibility MAY be provided via the &jep0004; protocol, as described below.

 diff --git a/xep-0077.xml b/xep-0077.xml index fe1b99b9..fd11833d 100644 --- a/xep-0077.xml +++ b/xep-0077.xml @@ -7,7 +7,7 @@
In-Band Registration - This JEP documents a protocol for in-band registration with instant messaging servers and associated services using the jabber:iq:register namespace. + This specification documents a protocol for in-band registration with instant messaging servers and associated services using the jabber:iq:register namespace. &LEGALNOTICE; 0077 Final diff --git a/xep-0114.xml b/xep-0114.xml index cea56b25..be391fa2 100644 --- a/xep-0114.xml +++ b/xep-0114.xml @@ -7,7 +7,7 @@
Jabber Component Protocol - This JEP documents the existing protocol used for communication between servers and "external" components over the Jabber network. + This specification documents the existing protocol used for communication between servers and "external" components over the Jabber network. &LEGALNOTICE; 0114 Active diff --git a/xep-0126.xml b/xep-0126.xml index 2a8f20bb..25c76ad3 100644 --- a/xep-0126.xml +++ b/xep-0126.xml @@ -1,13 +1,13 @@ - + %ents; ]> - - + +
Invisibility - This JEP describes best practices regarding implementation of invisible presence by means of XMPP privacy lists. + This specification defines best practices regarding implementation of invisible presence by means of XMPP privacy lists. &LEGALNOTICE; 0126 Active @@ -59,7 +59,7 @@
-

Several popular instant messaging services implement a feature known as invisibility: the ability to remain online yet appear offline to some or all of one's contacts. A number of Jabber servers and clients have also implemented such a feature, using special values of the &PRESENCE; element's 'type' attribute (e.g., <presence type='invisible'/>). Unfortunately, such implementations are not compliant with &xmppcore; and &xmppim;, which specify that only the 'type' attribute values defined in the XML schema for the 'jabber:client' and 'jabber:server' namespaces are allowed in XMPP (and those values do not include "invisible"). However, RFC 3921 also defines a privacy lists protocol (i.e., the 'jabber:iq:privacy' namespace) that can be used to implement invisibility in an XMPP-compliant manner. This JEP documents how to do just that.

+

Several popular instant messaging services implement a feature known as invisibility: the ability to remain online yet appear offline to some or all of one's contacts. A number of Jabber servers and clients have also implemented such a feature, using special values of the &PRESENCE; element's 'type' attribute (e.g., <presence type='invisible'/>). Unfortunately, such implementations are not compliant with &xmppcore; and &xmppim;, which specify that only the 'type' attribute values defined in the XML schema for the 'jabber:client' and 'jabber:server' namespaces are allowed in XMPP (and those values do not include "invisible"). However, RFC 3921 also defines a privacy lists protocol (i.e., the 'jabber:iq:privacy' namespace) that can be used to implement invisibility in an XMPP-compliant manner. This specification documents how to do just that.

This document addresses the following requirements:

@@ -70,7 +70,7 @@ -

This JEP addresses the following use cases:

+

This document addresses the following use cases:

  1. Log In as Globally Invisible
  2. Become Selectively Visible
    3. @@ -410,15 +410,15 @@

    For security concerns related to privacy lists, refer to RFC 3921. Care must be taken regarding privacy lists, especially so that visibility/invisibility rules do not overwrite existing rules the user has set for the sake of security and privacy; for details, see the Implementation Notes section of this document.

    -

    It is important to recognize that invisibility can be defeated without more advanced privacy lists than those defined above and an awareness of context on the part of a client. For example, if a user usually logs in as the same resource (e.g., "Home"), a contact can send an IQ request to that resource's full JID using &jep0012;, &jep0030;, &jep0090;, or &jep0092; and receive a reply, thus providing information that reveals the user's availability. In addition, Last Activity requests sent by a subscribed contact to the user's bare JID will normally reveal the user's availability as well. To help ensure that the user's invisibility cannot be defeated in this way, the user's client SHOULD add IQ blocking to the relevant privacy list. Finally, the user's client SHOULD NOT return "is-composing" events as defined in &jep0022; or &jep0085;.

    +

    It is important to recognize that invisibility can be defeated without more advanced privacy lists than those defined above and an awareness of context on the part of a client. For example, if a user usually logs in as the same resource (e.g., "Home"), a contact can send an IQ request to that resource's full JID using &xep0012;, &xep0030;, &xep0090;, or &xep0092; and receive a reply, thus providing information that reveals the user's availability. In addition, Last Activity requests sent by a subscribed contact to the user's bare JID will normally reveal the user's availability as well. To help ensure that the user's invisibility cannot be defeated in this way, the user's client SHOULD add IQ blocking to the relevant privacy list. Finally, the user's client SHOULD NOT return "is-composing" events as defined in &xep0022; or &xep0085;.

     -

    This JEP requires no interaction with &IANA;.

    +

    This document requires no interaction with &IANA;.

     -

    No namespaces or parameters need to be registered with the ®ISTRAR; as a result of this JEP.

    +

    No namespaces or parameters need to be registered with the ®ISTRAR; as a result of this specification.

    The XML schema for the 'jabber:iq:privacy' namespace is defined in RFC 3921.

     - + diff --git a/xep-0143.xml b/xep-0143.xml index a9a08db6..f0e2fe3c 100644 --- a/xep-0143.xml +++ b/xep-0143.xml @@ -1,13 +1,13 @@ - + %ents; ]> - +
    - Guidelines for JEP Authors - This JEP provides information intended to assist authors of Jabber Enhancement Proposals. + Guidelines for Authors of XMPP Extension Protocols + This document provides information intended to assist authors of XMPP Extension Protocols. &LEGALNOTICE; 0143 Active @@ -15,7 +15,7 @@ Standards JIG Council - JEP-0001 + XEP-0001 @@ -25,7 +25,7 @@ 1.0 2004-12-09 psa -

    Per a vote of the Jabber Council, advanced status to Active.

     +

    Per a vote of the XMPP Council, advanced status to Active.

     0.4 @@ -43,81 +43,81 @@ 0.2 2004-09-16 psa -

    Described JEP metadata elements.

     +

    Described document metadata elements.

         0.1 2004-09-15 psa -

    Initial version (adapted from JEP template).

     +

    Initial version.
    -

    The &JSF; receives a significant number of proposals for defining extensions to the core XMPP protocols specified in &xmppcore;. 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 (JEP) 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 &jep0001;.

    +

    The &JSF; receives a significant number of proposals for defining extensions to the core XMPP protocols specified in &xmppcore;. However, it is not always clear to authors how to best structure a proposal in order for it to be accepted as an XMPP Extension Protocol (XEP) and then advance through the JSF's standards process. Therefore, this document provides guidelines that are intended to help authors write better XMPP Extension Protocol specifications.

    +

    These guidelines assume that the reader is familiar with the XEP series of documents and the processes for handling them within the JSF, as defined in &xep0001;.

     -

    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:

    +

    The prospective author is strongly encouraged to complete some research before submitting a proposal for consideration as an XMPP Extension Protocol. In particular, the author should do the following:

      -
    • Review the XMPP RFCs and experimental or approved JSF JEPs to determine if the proposed protocol extension is truly needed in order to fill a gap in existing Jabber/XMPP technologies and protocols.
      • -
    • Review rejected and deferred JEPs to determine if similar extensions have been proposed in the past but not approved by the &COUNCIL;.
      • +
    • Review the XMPP RFCs and experimental or approved XMPP Extension Protocols to determine if the proposed protocol extension is truly needed in order to fill a gap in existing Jabber/XMPP technologies and protocols.
      • +
    • Review rejected and deferred XMPP Extension Protocol specifications to determine if similar extensions have been proposed in the past but not approved by the &COUNCIL;.
    • Review protocols developed within other standards development organizations, such as the &IETF; and &W3C;, to determine if they might be more appropriate than a new XMPP extension.
    • Review discussions within the &SJIG; to determine if similar functionality has been discussed in the past or is currently under discussion.

    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:

      -
    1. Review JEP-0001 and the &jep0134;.
      2. +
    2. Review XEP-0001 and the &xep0134;.
    3. Understand the Submission Process.
      4. -
    4. Become familiar with the JEP XML Format.
      5. -
    5. Then and only then write a proposal that includes all of the appropriate Sections of a JEP.
      6. -
    6. Review the content to ensure that it conforms to the JEP Styleguide.
      7. +
    7. Become familiar with the XEP XML Format.
      8. +
    8. Then and only then write a proposal that includes all of the appropriate Sections of a XEP.
      9. +
    9. Review the content to ensure that it conforms to the XEP Styleguide.
     -

    The process for submitting a JEP is straightforward:

    +

    The process for submitting a proposal for consideration as an XMPP Extension Protocol is straightforward:

    1. Contact the &EDITOR; so that he knows to expect your submission.
    2. Write your proposal following the guidelines described herein.
    3. Make sure you read, understand, and agree to the &JSFIPR; before you submit your proposal.
      4. -
    4. Send your XML file (or a URL for the file) to the JEP Editor.
      5. +
    5. Send your XML file (or a URL for the file) to the XMPP Extensions Editor.
     - -

    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 <http://www.xml.com/pub/a/tools/ruwf/check.html>.

    -

    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.

    + +

    The XEP XML format is substantially similar to a reduced set of XHTML. This is intentional: it makes authoring XMPP Extension Protocol specifications easier. In fact, if you use the 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 XEP authoring and describe the XML format used for XMPP Extension Protocols (see the xep.xsd or xep.dtd file for a formal description).

    + +

    The best way to start working on your proposal is to retrieve all of the existing XMPP Extension Protocol specifications and associated stylesheets from source control. These files are stored using the CVS system, in a CVS module labelled 'xmpp' and subdirectory labelled 'extensions' 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 an XMPP Extension Protocol. In addition, a handy template file is included as the 'xep-template.xml' file in the 'extensions' directory, providing a quick starting point for XEP authoring.

    +

    To create your proposal, do a CVS checkout of the 'xmpp' module, change directories to the 'extensions/' directory, copy the template file (e.g., 'cp xep-template.xml xep-foo.xml'), 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 document in most modern web browsers as an XML file as long as you have xep.xsl and xep.dtd in the 'extensions/' directory. 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 XMPP Extensions Editor. If your XML file doesn't render at all (i.e., it's just one big text blob), you are using a bad browser. If you see only the bare outline generated by xep.xsl but none of your text, you have an error in your XML. You can check your XML syntax at xml.com <http://www.xml.com/pub/a/tools/ruwf/check.html>.

    +

    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 XMPP Extensions Editor will do the final rendering of XML into HTML as well as posting of your HTML file to www.xmpp.org, so you do not need to generate HTML files for submission to the XMPP Extensions Editor (in fact, the XMPP Extensions Editor requires that you submit your proposal in the XEP XML format, not HTML).

    +

    Finally, the jep.ent file contains convenient "external entities" that provide shortcuts for including references to XMPP Extension Protocols, 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 XMPP Extensions 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 XMPP Extensions 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.

    +

    This section describes the metadata elements contained in the <header/> element of a XEP file (see below for the file contents).

    +

    The XML character data of the <title/> element is the title of your XEP. Choose a descriptive title that is less than five words long. The XMPP Extensions 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 document defines a protocol that..."). The XMPP Extensions 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 - 2006 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/).

    -

    The XML character data of the <number/> element SHOULD be "xxxx"; this will be changed to the next sequential JEP number by the JEP Editor if the Jabber Council accepts the proposal as a JEP.

    -

    The XML character data of the <status/> element SHOULD be "ProtoJEP" since all proposals start out as "proto-JEPs"; this will be changed to "Experimental" if the Jabber Council accepts the proposal as a JEP.

    -

    The XML character data of the <type/> element SHOULD be either "Standards Track" or "Informational" (there are also Historical, Humorous, 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., &jep0126;).

    +

    This XMPP Extension Protocol is copyright 1999 - 2006 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy (<http://www.xmpp.org/extensions/ipr-policy.shtml>). This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>).

    +

    The XML character data of the <number/> element SHOULD be "xxxx"; this will be changed to the next sequential XEP number by the XMPP Extensions Editor if the XMPP Council accepts the proposal as an XMPP Extensions Protocol.

    +

    The XML character data of the <status/> element SHOULD be "ProtoXEP" since all proposals start out as "proto-XEPs"; this will be changed to "Experimental" if the XMPP Council accepts the proposal as an XMPP Extensions Protocol.

    +

    The XML character data of the <type/> element SHOULD be either "Standards Track" or "Informational" (there are also Historical, Humorous, and Procedural XEPs, but these are uncommon and usually written by the XMPP Extensions Editor). A Standards Track XEP defines a XMPP extension intended to be used as a common part of Jabber/XMPP technologies. An Informational XEP defines best practices or a usage profile related to XMPP or an XMPP Extension Protocol (e.g., &xep0175;).

    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 understood 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.

    +

    The <dependencies/> element is used to specify RFCs, XMPP Extension Protocols, and other specifications on which your proposal depends in a normative fashion (i.e., specifications that MUST or SHOULD be understood in order to implement your proposed protocol). Each specification MUST be identified by a distinct <spec/> child element (see existing XEP specifications for clues regarding document identifiers, or consult with the XMPP Extensions Editor).

    +

    The <supersedes/>, <supersededby/>, <shortname/>, and <schemaloc/> elements are for use by the XMPP Extensions Editor; however, if your document supersedes an existing XMPP Extension Protocol, feel free to include a <spec/> child element specifying the document identifier (e.g., XEP-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 XEP-0001.

    +

    Include one <revision/> element for each revision of your document. The XML character data of the <version/> element SHOULD be "0.0.1" for your initial submission to the XMPP Extensions 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 from XHTML: <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).

    +

    Aside from the metadata in the <header/> element (see above), a XEP 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 document. The allowable elements within a section element probably look familiar from XHTML: <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 XEP specifications).

    The <p/> and <li/> elements can also contain more markup that is familiar from XHTML, 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 XHTML 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., &jep0071; 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.

    + +

    Most XEP specifications will have most of the following sections, usually in something like the order shown. Other sections may be appropriate (e.g., &xep0071; 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 XMPP Extensions 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:

    +

    The introduction to a XEP document is quite important since it provides the rationale for considering the proposal. In particular, the introduction SHOULD include information such as the following:

    1. Tasks that users currently cannot complete because we are lacking the protocol you propose. (Note: Users are not just IM users, but any person, system, or application that could gain value from interacting with other entities over Jabber/XMPP networks.)
    2. Other projects or protocols and how Jabber/XMPP technologies could interface with them because of your proposed protocol (e.g., XML-RPC, SOAP).
      3. @@ -127,20 +127,20 @@
    -

    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.

    +

    Every XEP document SHOULD include a section describing the requirements being addressed by the document. 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 glossary.

    +

    If your XEP document uses terms that may not be familiar to the reader, please define them in a glossary.

     -

    It is recommended that JEP authors structure their proposals according to the use cases that the proposal will address. A good introduction to use cases may be found at <http://www.pols.co.uk/usecasezone/>. 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 &jep0045;, for example. Include one subsection for each use case.

    +

    It is recommended that document authors structure their proposals according to the use cases that the proposal will address. A good introduction to use cases may be found at <http://www.pols.co.uk/usecasezone/>. We have found that use cases force 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 &xep0045;, for example. Include one subsection for each use case.

    When writing use cases and the associated protocols, make sure to:

    • Clearly define the success scenarios, alternate flows, and possible errors.
      • -
    • Describe the expected behavior of Jabber clients, servers, and components when using this protocol.
      • +
    • Describe the expected behavior of Jabber/XMPP clients, servers, and components when using this protocol.
    • Include lots of protocol examples.
    -

    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:

    +

    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 XMPP Council. You get extra credit with the XMPP Extensions Editor if you follow Jabber tradition by using characters and situations from the plays of Shakespeare:

     -

    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.

    +

    If your proposal defines a number of error and status codes (as is done in XEP-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.

    @@ -166,22 +166,22 @@

    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 &rfc3552;.

     -

    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 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 document requires no interaction with the Internet Assigned Numbers Authority (IANA)." If your proposal requires interaction with the IANA, discuss the matter with the XMPP Extensions 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.

    + +

    This section is REQUIRED. The XMPP 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 XMPP Registrar, the text of this section SHOULD read "No namespaces or parameters need to be registered with the XMPP Registrar as a result of this document." Refer to Draft or Final XEPs for appropriate text in other cases, or consult with the XMPP Extensions 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.

    +

    An XML Schema is required in order for protocols to be approved by the XMPP Council. The XMPP Extensions 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.

    +

    Some XEP documents end with a section thanking non-authors who have made significant contributions to the specification; if that is true of your document, feel free to include this section.

         - -

    Note: JEP authors can consider this section as a kind of "Implementation Notes". :-)

    -

    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 With all due respect to authors in other parts of the world, JEPs follow American spelling conventions; thus "authorisation" will be changed to "authorization" and such., 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 See <http://en.wikipedia.org/wiki/The_Elements_of_Style>. and The Chicago Manual of Style See <http://en.wikipedia.org/wiki/The_Chicago_Manual_of_Style>.; please refer to those resources for information about common English (especially American English) usage and to this styleguide for JEP-specific guidelines.

    + +

    Note: Authors of XMPP Extension Protocol specifications can consider this section as a kind of "Implementation Notes". :-)

    +

    XMPP Extension Protocols 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 XMPP Extensions Editor will correct any errors of grammar, spelling With all due respect to authors in other parts of the world, XMPP Extension Protocols follow American spelling conventions; thus "authorisation" will be changed to "authorization" and such., punctuation, and usage he may find in your proposal, but may not do so until your proposal is in the XMPP Council's queue for consideration. In addition, the XMPP Extensions 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 See <http://en.wikipedia.org/wiki/The_Elements_of_Style>. and The Chicago Manual of Style See <http://en.wikipedia.org/wiki/The_Chicago_Manual_of_Style>.; please refer to those resources for information about common English (especially American English) usage and to this styleguide for XEP-specific guidelines.

    When talking about an attribute by name, refer to it in single quotes. Example: the 'to' attribute.

    When talking about the value of an attribute, refer to it in double quotes. Example: the value of the 'subscription' attribute is "both".

    @@ -238,7 +238,7 @@

    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".

    +

    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 client communications is "5222".

         -     + diff --git a/xep-README.xml b/xep-README.xml index 03a0d209..8bd2e3c0 100644 --- a/xep-README.xml +++ b/xep-README.xml @@ -1,13 +1,13 @@ - + %ents; ]> - - + +
    - JEP Editor README - This document describes work processes followed by the JEP Editor. + XMPP Extensions Editor README + This document describes work processes followed by the XMPP Extensions Editor. &LEGALNOTICE; README Experimental @@ -15,29 +15,24 @@ N/A N/A - JEP-0001 - JEP-0053 + XEP-0001 + XEP-0053 N/A - - Peter - Saint-Andre - stpeter@jabber.org - stpeter@jabber.org - + &stpeter; 0.5 2005-05-26 psa - Adjusted to reflect ProtoJEP status. + Adjusted to reflect ProtoXEP status. 0.4 2005-03-16 psa - Converted to JEP format; adjusted to reflect server move. + Converted to XEP format; adjusted to reflect server move. 0.3 @@ -49,7 +44,7 @@ 0.2 2004-10-11 psa - Defined Jabber Registrar processes. + Defined XMPP Registrar processes. 0.1 @@ -62,69 +57,69 @@

    Since the inception of the &JSF;, the &EDITOR; has been Peter Saint-Andre. However, if he gets hit by a bus or is replaced by someone else, this document may prove useful.

    -

    The JEP Editor manages the JEP process as defined in &jep0001;. In addition, the JEP Editor functions as the Jabber Registrar as defined in &jep0053;. Read those documents first, since this README focuses on mechanics rather than philosophy.

    +

    The XMPP Extensions Editor manages the XMPP extensions process as defined in &xep0001;. In addition, the XMPP Extensions Editor functions as the XMPP Registrar as defined in &xep0053;. Read those documents first, since this README focuses on mechanics rather than philosophy.

     - + -

    There are several JEP-related functions performed by the JEP Editor:

    +

    There are several XEP-related functions performed by the XMPP Extensions Editor:

      -
    1. Accepting a JEP
      2. -
    2. Updating a JEP
      3. -
    3. Deferring a JEP
      4. -
    4. Retracting a JEP
      5. +
    5. Accepting a XEP
      6. +
    6. Updating a XEP
      7. +
    7. Deferring a XEP
      8. +
    8. Retracting a XEP
    9. Issuing a Last Call
    10. Counting Council Votes
      11. -
    11. Advancing a JEP
      12. +
    12. Advancing a XEP

    These functions are specified below.

    - +

    Periodically, people send mail to editor@jabber.org with new proposals. Here is how to process such submissions.

    1. Receive proposal from author.
      2. -
    2. Give it a descriptive filename that does not include the string 'jep' or a JEP number.
      3. +
    3. Give it a descriptive filename that does not include the string 'xep' or a XEP number.
    4. Set the version to 0.0.1 if no version found.
      5. -
    5. Set the status to ProtoJEP.
      6. +
    6. Set the status to ProtoXEP.
    7. Convert XML to HTML and check the results for accuracy.
      8. -
    8. Place HTML at http://www.jabber.org/jeps/inbox/ (/var/www/jabber.org/jeps/inbox/)
      9. -
    9. Place XML in the editor's working CVS directory on webserver (e.g., ~/cvs/jeps/inbox/docname.xml)
      10. -
    10. Send a note to the Standards-JIG list by running the "protojep.py" script.
      11. -
    11. Wait until the Council decides whether to accept the proposal as a JEP (this may involve poking the Council Chair).
      12. +
    12. Place HTML at http://www.xmpp.org/extensions/inbox/ (/var/www/xmpp.org/extensions/inbox/)
      13. +
    13. Place XML in the editor's working CVS directory on webserver (e.g., ~/cvs/xmpp/extensions/inbox/docname.xml)
      14. +
    14. Send a note to the Standards-JIG list by running the "protoxep.py" script.
      15. +
    15. Wait until the Council decides whether to accept the proposal as a XEP (this may involve poking the Council Chair).
    16. If rejected, retain in the "inbox".

    17. If accepted, do the following:

        -
      1. Assign the JEP the next available number in the JEP series.
        2. +
      2. Assign the XEP the next available number in the XEP series.
      3. Modify the <number/> element in the XML file.
      4. Set the version to 0.1.
      5. Set the status to Experimental.
      6. Check the file for egregious errors.
        7. -
      7. Add the directory and XML file to the "jeps" CVS module.
        8. -
      8. Add a reference for the new JEP in the jep.ent file.
        9. +
      9. Add the directory and XML file to the "xmpp/extensions" CVS module.
        10. +
      10. Add a reference for the new XEP in the xep.ent file.
      11. Update CVS on the server.
      12. Run the "gen.sh" script.
      13. Run the "announce.py" script (see below), which updates the database and sends a message to the Standards-JIG list.
        14. -
      14. Redirect the "inbox" file to the new JEP URL.
        15. +
      15. Redirect the "inbox" file to the new XEP URL.
     - -

    Once a JEP has been published, it will be periodically updated in CVS, and sometimes those changes are significant enough to warrant a new version (e.g., version 0.2 after 0.1). Often a request to release a new version will come from the JEP author, sometimes from the Council (e.g., after the JEP has reached version 1.0 or version 2.0). Here is how to update JEPs.

    + +

    Once a XEP has been published, it will be periodically updated in CVS, and sometimes those changes are significant enough to warrant a new version (e.g., version 0.2 after 0.1). Often a request to release a new version will come from the document author, sometimes from the Council (e.g., after the XEP has reached version 1.0 or version 2.0). Here is how to update a XEP.

    1. Compile the file locally and check the content for accuracy (including the correct date and version number).
    2. Check your changes into CVS.
    3. Update CVS on the server.
      4. -
    4. Run the "archive.sh" script to put the previous JEP version in the "attic".
      5. +
    5. Run the "archive.sh" script to put the previous XEP version in the "attic".
    6. Run the "gen.sh" script.
    7. Run the "announce.py" script.
     - -

    The status of a JEP shall be automatically changed to Deferred if a new version has not been released in 6 months, except if the JEP is actively in the Council queue for consideration of issuance of a Last Call. Here is the process.

    + +

    The status of a XEP shall be automatically changed to Deferred if a new version has not been released in 6 months, except if the XEP is actively in the Council queue for consideration of issuance of a Last Call. Here is the process.

    1. Change the <status/> element to "Deferred" in the XML file.
    2. Check your changes into CVS (note: do not modify the version number!).
      3. @@ -134,12 +129,12 @@
    - -

    Sometimes an author retracts a JEP because it is no longer worthy of consideration. Here is the process.

    + +

    Sometimes an author retracts a XEP because it is no longer worthy of consideration. Here is the process.

    1. Change the <status/> element to "Retracted" in the XML file.
      2. -
    2. Modify the <abstract/> element with appropriate content (see existing Retracted JEPs).
      3. -
    3. Add a new revision block with an incremented version number, explaining that the JEP has been Retracted and why (see existing Retracted JEPs).
      4. +
    4. Modify the <abstract/> element with appropriate content (see existing Retracted XEPs).
      5. +
    5. Add a new revision block with an incremented version number, explaining that the XEP has been Retracted and why (see existing Retracted XEPs).
    6. Check your changes into CVS.
    7. Update CVS on the server.
    8. Run the "gen.sh" script.
      9. @@ -148,7 +143,7 @@ -

      The Jabber Council determines whether and when to issue a Last Call on an Experimental JEP. Here is the process.

      +

      The XMPP Council determines whether and when to issue a Last Call on an Experimental XEP. Here is the process.

      1. Receive notice from the Council Chair that a Last Call shall be issued.
      2. Determine the ending date, which must be at least 10 days in the future and usually is 2 weeks (sometimes 3 weeks if much discussion is expected).
        3. @@ -156,74 +151,72 @@
      3. Check your changes into CVS.
      4. Update CVS on the server.
      5. Run the "lastcall.py" script, which updates the database and sends a message to the Standards-JIG list.
        6. -
      6. Review the Jabber Registrar Considerations section to ensure accuracy.
        7. +
      7. Review the XMPP Registrar Considerations section to ensure accuracy.
       -

      The JEP Editor is responsible for counting the votes of Council members. The process is as follows.

      +

      The XMPP Extensions Editor is responsible for counting the votes of Council members. The process is as follows.

      1. Inform the Council of the vote (see examples in the council@jabber.org archives).
      2. Monitor the Council list and Council meetings for votes.
      3. Update the votes XML file contained in the "council" CVS module.
      4. Check your changes into CVS.
      5. Update CVS on the server.
        6. -
      6. Run the "gen.sh" script in the "council" module (don't confuse this with the JEP gen.sh script).
        7. -
      7. When all Council members have voted, update the JEP accordingly (see below on Advancing a JEP).
        8. +
      8. Run the "gen.sh" script in the "council" module (don't confuse this with the XEP gen.sh script).
        9. +
      9. When all Council members have voted, update the XEP accordingly (see below on Advancing a XEP).
       - -

      When the Council approves a JEP, it advances to either Draft (Standards Track JEPs) or Active (other JEP types). Here is the process.

      + +

      When the Council approves a XEP, it advances to either Draft (Standards Track XEPs) or Active (other XEP types). Here is the process.

      1. Change the <status/> element to "Active" or "Draft" as appropriate.
        2. -
      2. Add a new revision block with a version number of "1.0" (see existing JEPs for appropriate remarks).
        3. -
      3. If there are any XML schemas associated with the JEP, do the following: +
      4. Add a new revision block with a version number of "1.0" (see existing XEPs for appropriate remarks).
        5. +
      5. If there are any XML schemas associated with the XEP, do the following:
        1. Add an annotation to each schema (see existing examples).
          2. -
        2. In the directory for this JEP, create one .xsd file for each schema.
          3. -
        3. For each schema, add a <schemaloc/> element to the JEP file.
          4. -
        4. Create a /var/www/jabber.org/protocol/shortname/ directory on the server (replace "shortname" with the short name of the JEP).
          5. +
        5. In the 'schemas/' directory, create one .xsd file for each schema.
          6. +
        6. For each schema, add a <schemaloc/> element to the XEP file.
        7. Update the "schemagen.sh" script.
        6. -
      6. Add the protocol namespace (if any) to the protocol namespaces registry and complete any other Jabber Registrar actions called for in the JEP (see below).
        7. +
      7. Add the protocol namespace (if any) to the protocol namespaces registry and complete any other XMPP Registrar actions called for in the XEP (see below).
      8. Check your changes into CVS.
      9. Update CVS on the server.
        10. -
      10. Run the "archive.sh" script to put the previous JEP version in the "attic".
        11. +
      11. Run the "archive.sh" script to put the previous XEP version in the "attic".
      12. Run the "schemagen.sh" script if appropriate.
      13. Run the "gen.sh" script.
      14. Run the "announce.py" script.
        15. -
      15. Add a link to JEP from the appropriate section of the http://www.jabber.org/protocol/ page.
       - + - -

      Registry files are contained in the "registry" CVS module. In general, there are several files that may need to be updated when a JEP advances to Active or Draft. In particular, most JEPs specify one or more protocol namespaces, which need to be added to the namespaces.xml file in the "registry" module. Refer to the list of registries at http://www.jabber.org/registrar/ in order to determine which other registries may need to be updated. The reg.ent file will probably need to be updated as well. Once the Registrar actions have been completed, update the text of the JEP's Jabber Registrar Considerations section accordingly (e.g., to change "shall include" to "includes").

      + +

      Registry files are contained in the "registry" CVS module. In general, there are several files that may need to be updated when a XEP advances to Active or Draft. In particular, most XEPs specify one or more protocol namespaces, which need to be added to the namespaces.xml file in the "registry" module. Refer to the list of registries at http://www.xmpp.org/registrar/ in order to determine which other registries may need to be updated. The reg.ent file will probably need to be updated as well. Once the Registrar actions have been completed, update the text of the XEP's XMPP Registrar Considerations section accordingly (e.g., to change "shall include" to "includes").

       -

      A JEP may call for one or more new registries to be created. If so, carefully review the Jabber Registrar Considerations section of the JEP before it advances to Draft or Active in order to provide appropriate feedback to the JEP author. (Alternatively, make the changes directly in the JEP file in consultation with the author.)

      -

      When creating a new registry, it is best to copy the DTD, XML, and XSL files for an existing registry, then modify them in accordance with the definition of the new registry in the relevant JEP. The gen.sh script will need to be updated to reflect the existence of the new registry, as will the index file for the http://www.jabber.org/registrar/ web page.

      -

      Check all your changes into CVS, update your CVS directory on the web server, and run the gen.sh script to update the Jabber Registrar web pages.

      +

      A XEP may call for one or more new registries to be created. If so, carefully review the XMPP Registrar Considerations section of the XEP before it advances to Draft or Active in order to provide appropriate feedback to the XEP author. (Alternatively, make the changes directly in the XEP file in consultation with the author.)

      +

      When creating a new registry, it is best to copy the DTD, XML, and XSL files for an existing registry, then modify them in accordance with the definition of the new registry in the relevant XEP. The gen.sh script will need to be updated to reflect the existence of the new registry, as will the index file for the http://www.xmpp.org/registrar/ web page.

      +

      Check all your changes into CVS, update your CVS directory on the web server, and run the gen.sh script to update the XMPP Registrar web pages.

             -

      In order to convert XML files into HTML and other formats, the JEP Editor currently uses the xsltproc tool, which is part of libxml2 (created by Daniel Veillard). This tool is extremely handy and it is recommended that use of xsltproc be continued, especially since the shell scripts (described below) make calls to xsltproc.

      +

      In order to convert XML files into HTML and other formats, the XMPP Extensions Editor currently uses the xsltproc tool, which is part of libxml2 (created by Daniel Veillard). This tool is extremely handy and it is recommended that use of xsltproc be continued, especially since the shell scripts (described below) make calls to xsltproc.

       -

      Most the "magic" behind creating the HTML-formatted JEPs, as well as the IETF-style reference files, is perfomed by XSL stylesheets. The main file here is jep.xsl, although ref.xsl is used to create the reference files. A future version of this README may explain these files in more depth.

      +

      Most the "magic" behind creating the HTML-formatted XEPs, as well as the IETF-style reference files, is perfomed by XSL stylesheets. The main file here is xep.xsl, although ref.xsl is used to create the reference files. A future version of this README may explain these files in more depth.

       -

      The jep.ent file contains handy references that can be incorporated into any JEP XML document, thus providing a centralized location for various document references. The JEP Editor must keep this file up to date (e.g., by adding all new JEPs to it), and should be the only person who makes changes to the file.

      +

      The xep.ent file contains handy references that can be incorporated into any XEP XML document, thus providing a centralized location for various document references. The XMPP Extensions Editor must keep this file up to date (e.g., by adding all new XEPs to it), and should be the only person who makes changes to the file.

       @@ -231,19 +224,19 @@

      1. announce.py

        -

        This script announces a new version of a JEP by updating the database and sending a message to standards-jig@jabber.org.

        +

        This script announces a new version of a XEP by updating the database and sending a message to standards-jig@jabber.org.

      2. deferrred.py

        -

        This script updates the database and sends a message to standards-jig@jabber.org when the status of a JEP is changed to Deferred. Before running this script, make sure that you modify the <status/> element in the JEP itself and run the gen.sh shell script.

        +

        This script updates the database and sends a message to standards-jig@jabber.org when the status of a XEP is changed to Deferred. Before running this script, make sure that you modify the <status/> element in the XEP itself and run the gen.sh shell script.

      3. lastcall.py

        -

        This script announces a Last Call for a JEP by updating the database and sending a message to standards-jig@jabber.org.

        +

        This script announces a Last Call for a XEP by updating the database and sending a message to standards-jig@jabber.org.

      4. -

        protojep.py

        -

        This script announces availability of a new "proto-JEP" (i.e., a document not yet accepted as a JEP by the Jabber Council) by sending a message to standards-jig@jabber.org. Before running this script, place the new proto-JEP so that it is available at http://www.jabber.org/jeps/inbox/ (normally this is done by running 'xsltproc inbox/docname.xml > /var/www/jabber.org/jeps/inbox/docname.html' from the editor's working CVS directory on the web server).

        +

        protoxep.py

        +

        This script announces availability of a new "proto-XEP" (i.e., a document not yet accepted as a XEP by the XMPP Council) by sending a message to standards-jig@jabber.org. Before running this script, place the new proto-XEP so that it is available at http://www.xmpp.org/extensions/inbox/ (normally this is done by running 'xsltproc inbox/docname.xml > /var/www/xmpp.org/extensions/inbox/docname.html' from the editor's working CVS directory on the web server).

      @@ -253,22 +246,22 @@

      1. all.sh

        -

        This script converts all JEP XML files into HTML. Use this if the jep.xsl file changes in ways that affect all JEPs. But make sure that CVS is synced up first -- you don't want to be publishing interim versions of JEPs!

        +

        This script converts all XEP XML files into HTML. Use this if the xep.xsl file changes in ways that affect all XEPs. But make sure that CVS is synced up first -- you don't want to be publishing interim versions of XEPs!

      2. archive.sh

        -

        This script archives the version of a JEP currently on the website. Run this script before publishing a new version!

        +

        This script archives the version of a XEP currently on the website. Run this script before publishing a new version!

      3. gen.sh

        -

        This script converts one JEP XML file into HTML. Run this script before announcing a new version. This script can also be used for minor edits to the current version.

        +

        This script converts one XEP XML file into HTML. Run this script before announcing a new version. This script can also be used for minor edits to the current version.

      4. schemagen.sh

        -

        This script updates all of the XML schemas located at http://www.jabber.org/protocol/ (more accurately, the subdirectories there). Update this file every time a protocol JEP with an associated schema advances to Active or Draft.

        +

        This script updates all of the XML schemas located at <http://www.xmpp.org/schemas/>. Update this file every time a protocol XEP with an associated schema advances to Active or Draft.

             - + diff --git a/xep-template.xml b/xep-template.xml index f22be195..340a618a 100644 --- a/xep-template.xml +++ b/xep-template.xml @@ -1,22 +1,22 @@ - + %ents; ]> - - + +
      - JEP Template - An example of the format for Jabber Enhancement Proposals. - This Jabber Enhancement Proposal is copyright 1999 - 2005 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/). + XEP Template + An example of the format for XMPP Extension Protocols. + This XMPP Extension Protocol is copyright 1999 - 2006 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy (<http://www.xmpp.org/extensions/ipr-policy.shtml>). This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>). xxxx - ProtoJEP + ProtoXEP Standards Track Standards JIG Council XMPP Core - JEP-0001 + XEP-0001 Etc. @@ -36,7 +36,7 @@
      -

      This is a template for use in writing Jabber Enhancement Proposals. For detailed information about the JEP process and how to write a JEP, refer to "JEP-0001: Jabber Enhancement Proposals" and "JEP-0143: Guidelines for JEP Authors".

      +

      This is a template for use in writing Jabber Enhancement Proposals. For detailed information about the XEP process and how to write an XMPP Extension Protocol specification, refer to "XEP-0001: XMPP Extension Protocols" and "XEP-0143: Guidelines for Authors of XMPP Extension Protocols".

      STRONGLY RECOMMENDED.

      @@ -66,6 +66,6 @@

      REQUIRED.

       -

      REQUIRED for protocol JEPs.

      +

      REQUIRED for protocol XEPs.

       -       + diff --git a/xep.dtd b/xep.dtd index 271db089..a3fa1a98 100644 --- a/xep.dtd +++ b/xep.dtd @@ -1,6 +1,6 @@ - + diff --git a/xep.ent b/xep.ent index 278c790c..6d0602df 100644 --- a/xep.ent +++ b/xep.ent @@ -1,11 +1,13 @@ @@ -36,22 +38,22 @@ -http://www.jabber.org/registrar/amp-actions.html>"> -http://www.jabber.org/registrar/amp-conditions.html>"> -http://www.jabber.org/registrar/errors.html>"> -http://www.jabber.org/registrar/compress.html>"> -http://www.jabber.org/registrar/disco-categories.html>"> -http://www.jabber.org/registrar/disco-features.html>"> -http://www.jabber.org/registrar/disco-nodes.html>"> -http://www.jabber.org/registrar/formtypes.html>"> -http://www.jabber.org/registrar/mucstatus.html>"> -http://www.jabber.org/registrar/namespaces.html>"> -http://www.jabber.org/registrar/querytypes.html>"> -http://www.jabber.org/registrar/shim.html>"> -http://www.jabber.org/registrar/si-profiles.html>"> -http://www.jabber.org/registrar/stream-features.html>"> -http://www.jabber.org/registrar/xdv-prefixes.html>"> -http://www.jabber.org/registrar/xdv-datatypes.html>"> +http://www.xmpp.org/registrar/amp-actions.html>"> +http://www.xmpp.org/registrar/amp-conditions.html>"> +http://www.xmpp.org/registrar/errors.html>"> +http://www.xmpp.org/registrar/compress.html>"> +http://www.xmpp.org/registrar/disco-categories.html>"> +http://www.xmpp.org/registrar/disco-features.html>"> +http://www.xmpp.org/registrar/disco-nodes.html>"> +http://www.xmpp.org/registrar/formtypes.html>"> +http://www.xmpp.org/registrar/mucstatus.html>"> +http://www.xmpp.org/registrar/namespaces.html>"> +http://www.xmpp.org/registrar/querytypes.html>"> +http://www.xmpp.org/registrar/shim.html>"> +http://www.xmpp.org/registrar/si-profiles.html>"> +http://www.xmpp.org/registrar/stream-features.html>"> +http://www.xmpp.org/registrar/xdv-prefixes.html>"> +http://www.xmpp.org/registrar/xdv-datatypes.html>"> @@ -118,7 +120,7 @@ -This Jabber Enhancement Proposal is copyright 1999 - 2006 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.shtml>. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>)." > +This XMPP Extension Protocol is copyright 1999 - 2006 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy <http://www.xmpp.org/extensions/ipr-policy.shtml>. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>)." > @@ -126,7 +128,7 @@ In accordance with Section 3.2.2.1 of XML Schema Part 2: Datatypes, the allowable lexical representations for the xs:boolean datatype are the strings "0" and "false" for the concept 'false' and the strings "1" and "true" for the concept 'true'; implementations MUST support both styles of lexical representation." > -In order to submit new values to this registry, the registrant must define an XML fragment of the following form and either include it in the relevant Jabber Enhancement Proposal or send it to the email address <registrar@jabber.org>:

      " > +In order to submit new values to this registry, the registrant must define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address <registrar@jabber.org>:

      " > @@ -136,17 +138,17 @@ JSF Board of Directors The JSF Board of Directors is an elected body that possesses overall responsibility for the affairs of the Jabber Software Foundation. For further information, see <http://www.jabber.org/board/>." > JSF Bylaws The Bylaws of the Jabber Software Foundation (JSF) define the legal basis and operating procedures of the JSF. For further information, see <http://www.jabber.org/jsf/bylaws.shtml>." > -Jabber Council 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/>." > -JEP Editor 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.shtml>." > -Jabber Software Foundation (JSF) 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/>." > -JSF-IETF list The JSF-IETF list is for discussion of matters of mutual interest to the Jabber Software Foundation and the Internet Engineering Task Force. The primary focus of the list is technical, mainly regarding JSF use of IETF technologies (e.g., references to RFCs in JEPs) and IETF use of JSF technologies (e.g., references to JEPs in Internet-Drafts and RFCs). To subscribe to the list or view the list archives, visit <http://mail.jabber.org/mailman/listinfo/jsf-ietf/>." > -JSF IPR Policy 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.shtml>." > -Jabber Registrar 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. For further information, see <http://www.jabber.org/registrar/>." > -Standards JIG 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/>." > +XMPP Council The XMPP Council is a technical steering committee, authorized by the JSF Board of Directors and elected by JSF members, that approves of new XMPP Extensions Protocols and oversees the JSF's standards process. For further information, see <http://www.xmpp.org/council/>." > +XMPP Extensions Editor The XMPP Extensions 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.xmpp.org/extensions/editor.shtml>." > +Jabber Software Foundation (JSF) The Jabber Software Foundation (JSF) is an independent, non-profit organization that develops open extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP). For further information, see <http://www.jabber.org/jsf/>." > +JSF-IETF list The JSF-IETF list is for discussion of matters of mutual interest to the Jabber Software Foundation and the Internet Engineering Task Force. The primary focus of the list is technical, mainly regarding JSF use of IETF technologies (e.g., references to RFCs in XMPP Extension Protocols) and IETF use of JSF technologies (e.g., references to XMPP Extension Protocols in Internet-Drafts and RFCs). To subscribe to the list or view the list archives, visit <http://mail.jabber.org/mailman/listinfo/jsf-ietf/>." > +JSF IPR Policy The JSF IPR Policy defines the Jabber Software Foundation's official policy regarding intellectual property rights (IPR) as they pertain to XMPP Extension Protocols (XEPs). For further information, see <http://www.xmpp.org/extensions/ipr-policy.shtml>." > +XMPP Registrar The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the Jabber Software Foundation. For further information, see <http://www.xmpp.org/registrar/>." > +Standards JIG The Standards JIG is a standing Jabber Interest Group devoted to development of XMPP Extension Protocols. The discussion list of the Standards JIG is the primary venue for discussion of Jabber/XMPP protocols, as well as for announcements by the XMPP Extensions Editor and XMPP Registrar. To subscribe to the list or view the list archives, visit <http://mail.jabber.org/mailman/listinfo/standards-jig/>." > -jabberd The jabberd server is the original server implementation of the Jabber protocols, first developed by Jeremie Miller, inventor of Jabber. For further information, see <http://jabberd.jabberstudio.org/>." > +jabberd The jabberd server is the original server implementation of the Jabber/XMPP protocols, first developed by Jeremie Miller, inventor of Jabber. For further information, see <http://jabberd.jabberstudio.org/>." > @@ -426,7 +428,7 @@ draft-saintandre-xmpp-simple Basic Messaging and Presence Interoperability between the Extensible Messaging and Presence Protocol (XMPP) and Session Initiation Protocol (SIP) for Instant Messaging and Presence Leveraging Extensions (SIMPLE) <http://www.ietf.org/internet-drafts/draft-saintandre-xmpp-simple-05.txt> (work in progress)." > XMPP URI A Uniform Resource Identifier (URI) Scheme for the Extensible Messaging and Presence Protocol (XMPP) <http://www.ietf.org/internet-drafts/draft-saintandre-xmpp-uri-08.txt> (work in progress)." > - + @@ -564,198 +566,198 @@ " > - + -Jabber Enhancement Proposals JEP-0001: Jabber Enhancement Proposals <http://www.jabber.org/jeps/jep-0001.html>." > -Jabber Interest Groups JEP-0002: Jabber Interest Groups <http://www.jabber.org/jeps/jep-0002.html>." > -Proxy Accept Socket Service JEP-0002: Proxy Accept Socket Service <http://www.jabber.org/jeps/jep-0003.html>." > -Data Forms JEP-0004: Data Forms <http://www.jabber.org/jeps/jep-0004.html>." > -IQ-Based Avatars JEP-0008: IQ-Based Avatars <http://www.jabber.org/jeps/jep-0008.html>." > -Jabber-RPC JEP-0009: Jabber-RPC <http://www.jabber.org/jeps/jep-0009.html>." > -Jabber Browsing JEP-0011: Jabber Browsing <http://www.jabber.org/jeps/jep-0011.html>." > -Last Activity JEP-0012: Last Activity <http://www.jabber.org/jeps/jep-0012.html>." > -Flexible Offline Message Retrieval JEP-0013: Flexible Offline Message Retrieval <http://www.jabber.org/jeps/jep-0013.html>." > - - -Server-Based Privacy Rules JEP-0016: Server-Based Privacy Rules <http://www.jabber.org/jeps/jep-0016.html>." > - -Invisible Presence JEP-0018: Invisible Presence <http://www.jabber.org/jeps/jep-0018.html>." > -Streamlining the JIGs JEP-0019: Streamlining the JIGs <http://www.jabber.org/jeps/jep-0019.html>." > -Feature Negotiation JEP-0020: Feature Negotiation <http://www.jabber.org/jeps/jep-0020.html>." > -Jabber Event Notification Service JEP-0021: Jabber Event Notification Service <http://www.jabber.org/jeps/jep-0021.html>." > -Message Events JEP-0022: Message Events <http://www.jabber.org/jeps/jep-0022.html>." > -Message Expiration JEP-0023: Message Expiration <http://www.jabber.org/jeps/jep-0023.html>." > -Publish/Subscribe JEP-0024: Publish/Subscribe <http://www.jabber.org/jeps/jep-0024.html>." > -Jabber HTTP Polling JEP-0025: Jabber HTTP Polling <http://www.jabber.org/jeps/jep-0025.html>." > -Internationalization JEP-0026: Internationalization <http://www.jabber.org/jeps/jep-0026.html>." > -Current Jabber OpenPGP Usage JEP-0027: Current Jabber OpenPGP Usage <http://www.jabber.org/jeps/jep-0027.html>." > - -Definition of Jabber Identifiers JEP-0029: Definition of Jabber Identifiers <http://www.jabber.org/jeps/jep-0029.html>." > -Service Discovery JEP-0030: Service Discovery <http://www.jabber.org/jeps/jep-0030.html>." > -A Framework for Securing Jabber Conversations JEP-0031: A Framework for Securing Jabber Conversations <http://www.jabber.org/jeps/jep-0031.html>." > -Jabber URI Scheme JEP-0032: Jabber URI Scheme <http://www.jabber.org/jeps/jep-0032.html>." > -Extended Stanza Addressing JEP-0033: Extended Stanza Addressing <http://www.jabber.org/jeps/jep-0033.html>." > -SASL Integration JEP-0034: SASL Integration <http://www.jabber.org/jeps/jep-0034.html>." > -SSL/TLS Integration JEP-0035: SSL/TLS Integration <http://www.jabber.org/jeps/jep-0035.html>." > -Pub-sub Subscriptions JEP-0036: Pub-sub Subscriptions <http://www.jabber.org/jeps/jep-0036.html>." > - -Icon Styles JEP-0038: Icon Styles <http://www.jabber.org/jeps/jep-0038.html>." > -Statistics Gathering JEP-0039: Statistics Gathering <http://www.jabber.org/jeps/jep-0039.html>." > -Robust Publish-Subscribe JEP-0040: Robust Publish-Subscribe <http://www.jabber.org/jeps/jep-0040.html>." > -Jidlink JEP-0041: Jidlink <http://www.jabber.org/jeps/jep-0041.html>." > -Jabber OOB Broadcast Service JEP-0042: Jabber OOB Broadcast Service <http://www.jabber.org/jeps/jep-0042.html>." > -Jabber Database Access JEP-0043: Jabber Database Access <http://www.jabber.org/jeps/jep-0043.html>." > -Full Namespace Support in XML Streams JEP-0044: Full Namespace Support in XML Streams <http://www.jabber.org/jeps/jep-0044.html>." > -Multi-User Chat JEP-0045: Multi-User Chat <http://www.jabber.org/jeps/jep-0045.html>." > -Direct TCP JEP-0046: Direct TCP <http://www.jabber.org/jeps/jep-0046.html>." > -In-Band Bytestreams JEP-0047: In-Band Bytestreams <http://www.jabber.org/jeps/jep-0047.html>." > -Bookmark Storage JEP-0048: Bookmark Storage <http://www.jabber.org/jeps/jep-0048.html>." > -Private XML Storage JEP-0049: Private XML Storage <http://www.jabber.org/jeps/jep-0049.html>." > -Ad-Hoc Commands JEP-0050: Ad-Hoc Commands <http://www.jabber.org/jeps/jep-0050.html>." > -Redirect and Connection Transfer JEP-0051: Redirect and Connection Transfer <http://www.jabber.org/jeps/jep-0051.html>." > -File Transfer JEP-0052: File Transfer <http://www.jabber.org/jeps/jep-0052.html>." > -Jabber Registrar JEP-0053: Jabber Registrar <http://www.jabber.org/jeps/jep-0053.html>." > -vcard-temp JEP-0054: vcard-temp <http://www.jabber.org/jeps/jep-0054.html>." > -Jabber Search JEP-0055: Jabber Search <http://www.jabber.org/jeps/jep-0055.html>." > -Business Data Interchange JEP-0056: Business Data Interchange <http://www.jabber.org/jeps/jep-0056.html>." > -Extended Roster JEP-0057: Extended Roster <http://www.jabber.org/jeps/jep-0057.html>." > -Multi-User Text Editing JEP-0058: Multi-User Text Editing <http://www.jabber.org/jeps/jep-0058.html>." > -Result Set Management JEP-0059: Result Set Management <http://www.jabber.org/jeps/jep-0059.html>." > -Publish-Subscribe JEP-0060: Publish-Subscribe <http://www.jabber.org/jeps/jep-0060.html>." > -Shared Notes JEP-0061: Shared Notes <http://www.jabber.org/jeps/jep-0061.html>." > -Packet Filtering JEP-0062: Packet Filtering <http://www.jabber.org/jeps/jep-0062.html>." > -Basic Filtering Operations JEP-0063: Basic Filtering Operations <http://www.jabber.org/jeps/jep-0063.html>." > -XPath Filtering JEP-0064: XPath Filtering <http://www.jabber.org/jeps/jep-0064.html>." > -SOCKS5 Bytestreams JEP-0065: SOCKS5 Bytestreams <http://www.jabber.org/jeps/jep-0065.html>." > -Out-of-Band Data JEP-0066: Out of Band Data <http://www.jabber.org/jeps/jep-0066.html>." > -Stock Data Transmission JEP-0067: Stock Data Transmission <http://www.jabber.org/jeps/jep-0067.html>." > -Field Standardization for Data Forms JEP-0068: Field Data Standardization for Data Forms <http://www.jabber.org/jeps/jep-0068.html>." > -Compliance JIG JEP-0069: Compliance JIG <http://www.jabber.org/jeps/jep-0069.html>." > -Verifying HTTP Requests via XMPP JEP-0070: Verifying HTTP Requests via XMPP <http://www.jabber.org/jeps/jep-0070.html>." > -XHTML-IM JEP-0071: XHTML-IM <http://www.jabber.org/jeps/jep-0071.html>." > -SOAP over XMPP JEP-0072: SOAP over XMPP <http://www.jabber.org/jeps/jep-0072.html>." > -Basic IM Protocol Suite JEP-0073: Basic IM Protocol Suite <http://www.jabber.org/jeps/jep-0073.html>." > -Simple Access Control JEP-0074: Simple Access Control <http://www.jabber.org/jeps/jep-0074.html>." > -Jabber Object Access Protocol JEP-0075: Jabber Object Access Protocol <http://www.jabber.org/jeps/jep-0075.html>." > -Malicious Stanzas JEP-0076: Malicious Stanzas <http://www.jabber.org/jeps/jep-0076.html>." > -In-Band Registration JEP-0077: In-Band Registration <http://www.jabber.org/jeps/jep-0077.html>." > -Non-SASL Authentication JEP-0078: Non-SASL Authentication <http://www.jabber.org/jeps/jep-0078.html>." > -Advanced Message Processing JEP-0079: Advanced Message Processing <http://www.jabber.org/jeps/jep-0079.html>." > -User Geolocation JEP-0080: User Geolocation <http://www.jabber.org/jeps/jep-0080.html>." > -Jabber MIME Type JEP-0081: Jabber MIME Type <http://www.jabber.org/jeps/jep-0081.html>." > -Jabber Date and Time Profiles JEP-0082: Jabber Date and Time Profiles <http://www.jabber.org/jeps/jep-0082.html>." > -Nested Roster Groups JEP-0083: Nested Roster Groups <http://www.jabber.org/jeps/jep-0083.html>." > -User Avatar JEP-0084: User Avatar <http://www.jabber.org/jeps/jep-0084.html>." > -Chat State Notifications JEP-0085: Chat State Notifications <http://www.jabber.org/jeps/jep-0085.html>." > -Error Condition Mappings JEP-0086: Error Condition Mappings <http://www.jabber.org/jeps/jep-0086.html>." > -Stream Initiation JEP-0087: Stream Initiation <http://www.jabber.org/jeps/jep-0087.html>." > -Client Webtabs JEP-0088: Client Webtabs <http://www.jabber.org/jeps/jep-0088.html>." > -Generic Alerts JEP-0089: Generic Alerts <http://www.jabber.org/jeps/jep-0089.html>." > -Entity Time JEP-0090: Entity Time <http://www.jabber.org/jeps/jep-0090.html>." > -Delayed Delivery JEP-0091: Delayed Delivery <http://www.jabber.org/jeps/jep-0091.html>." > -Software Version JEP-0092: Software Version <http://www.jabber.org/jeps/jep-0092.html>." > -Roster Item Exchange JEP-0093: Roster Item Exchange <http://www.jabber.org/jeps/jep-0093.html>." > -Agent Information JEP-0094: Agent Information <http://www.jabber.org/jeps/jep-0094.html>." > -Stream Initiation JEP-0095: Stream Initiation <http://www.jabber.org/jeps/jep-0095.html>." > -File Transfer JEP-0096: File Transfer <http://www.jabber.org/jeps/jep-0096.html>." > -iCal Envelope JEP-0097: iCal Envelope <http://www.jabber.org/jeps/jep-0097.html>." > -Enchanced Private XML Storage JEP-0098: Enchanced Private XML Storage <http://www.jabber.org/jeps/jep-0098.html>." > -IQ Query Action Protocol JEP-0099: IQ Query Action Protocol <http://www.jabber.org/jeps/jep-0099.html>." > -Gateway Interaction JEP-0100: Gateway Interaction <http://www.jabber.org/jeps/jep-0100.html>." > -HTTP Authentication using Jabber Tickets JEP-0101: HTTP Authentication using Jabber Tickets <http://www.jabber.org/jeps/jep-0101.html>." > -Security Extensions JEP-0102: Security Extensions <http://www.jabber.org/jeps/jep-0102.html>." > -URL Address Information JEP-0103: URL Address Information <http://www.jabber.org/jeps/jep-0103.html>." > -HTTP Scheme for URL Data JEP-0104: HTTP Scheme for URL Data <http://www.jabber.org/jeps/jep-0104.html>." > -Tree Transfer Stream Initiation Profile JEP-0105: Tree Transfer Stream Initiation Profile <http://www.jabber.org/jeps/jep-0105.html>." > -JID Escaping JEP-0106: JID Escaping <http://www.jabber.org/jeps/jep-0106.html>." > -User Mood JEP-0107: User Mood <http://www.jabber.org/jeps/jep-0107.html>." > -User Activity JEP-0108: User Activity <http://www.jabber.org/jeps/jep-0108.html>." > -Vacation Messages JEP-0109: Vacation Messages <http://www.jabber.org/jeps/jep-0109.html>." > -Generic Maps JEP-0110: Generic Maps <http://www.jabber.org/jeps/jep-0110.html>." > -A Transport for Initiating and Negotiating Sessions JEP-0111: A Transport for Initiating and Negotiating Sessions <http://www.jabber.org/jeps/jep-0111.html>." > -User Physical Location JEP-0112: User Physical Location <http://www.jabber.org/jeps/jep-0112.html>." > -Simple Whiteboarding JEP-0113: Simple Whiteboarding <http://www.jabber.org/jeps/jep-0113.html>." > -Jabber Component Protocol JEP-0114: Jabber Component Protocol <http://www.jabber.org/jeps/jep-0114.html>." > -Entity Capabilities JEP-0115: Entity Capabilities <http://www.jabber.org/jeps/jep-0115.html>." > -Encrypted Sessions JEP-0116: Encrypted Sessions <http://www.jabber.org/jeps/jep-0116.html>." > -Intermediate IM Protocol Suite JEP-0117: Intermediate IM Protocol Suite <http://www.jabber.org/jeps/jep-0117.html>." > -User Tune JEP-0118: User Tune <http://www.jabber.org/jeps/jep-0118.html>." > -Extended Presence Protocol Suite JEP-0119: Extended Presence Protocol Suite <http://www.jabber.org/jeps/jep-0119.html>." > -Infobits JEP-0120: Infobits <http://www.jabber.org/jeps/jep-0120.html>." > -Dublin Core Infobits Mapping JEP-0121: Dublin Core Infobits Mapping <http://www.jabber.org/jeps/jep-0121.html>." > -Data Forms Validation JEP-0122: Data Forms Validation <http://www.jabber.org/jeps/jep-0122.html>." > -Entity Metadata JEP-0123: Entity Metadata <http://www.jabber.org/jeps/jep-0123.html>." > -HTTP Binding JEP-0124: HTTP Binding <http://www.jabber.org/jeps/jep-0124.html>." > -vCard Infobits Mapping JEP-0125: vCard Infobits Mapping <http://www.jabber.org/jeps/jep-0125.html>." > -Invisibility JEP-0126: Invisibility <http://www.jabber.org/jeps/jep-0126.html>." > -Common Alerting Protocol (CAP) over XMPP JEP-0127: Common Alerting Protocol (CAP) over XMPP <http://www.jabber.org/jeps/jep-0127.html>." > -Service Discovery Extensions JEP-0128: Service Discovery Extensions <http://www.jabber.org/jeps/jep-0128.html>." > -WebDAV File Transfers JEP-0129: WebDAV File Transfers <http://www.jabber.org/jeps/jep-0129.html>." > -Waiting Lists JEP-0130: Waiting Lists <http://www.jabber.org/jeps/jep-0130.html>." > -Stanza Headers and Internet Metadata JEP-0131: Stanza Headers and Internet Metadata <http://www.jabber.org/jeps/jep-0131.html>." > -Presence Obtained via Kinesthetic Excitation (POKE) JEP-0132: Presence Obtained via Kinesthetic Excitation (POKE) <http://www.jabber.org/jeps/jep-0132.html>." > -Service Administration JEP-0133: Service Administration <http://www.jabber.org/jeps/jep-0133.html>." > -Protocol Design Guidelines JEP-0134: Protocol Design Guidelines <http://www.jabber.org/jeps/jep-0134.html>." > -File Sharing JEP-0135: File Sharing <http://www.jabber.org/jeps/jep-0135.html>." > -Message Archiving JEP-0136: Message Archiving <http://www.jabber.org/jeps/jep-0136.html>." > -Publishing Stream Initiation Requests JEP-0137: Publishing Stream Initiation Requests <http://www.jabber.org/jeps/jep-0137.html>." > -Stream Compression JEP-0138: Stream Compression <http://www.jabber.org/jeps/jep-0138.html>." > -Security JIG JEP-0139: Security JIG <http://www.jabber.org/jeps/jep-0139.html>." > -Shared Groups JEP-0140: Shared Groups <http://www.jabber.org/jeps/jep-0140.html>." > -Data Forms Layout JEP-0141: Data Forms Layout <http://www.jabber.org/jeps/jep-0141.html>." > -Workgroup Queues JEP-0142: Workgroup Queues <http://www.jabber.org/jeps/jep-0142.html>." > -Guidelines for JEP Authors JEP-0143: Guidelines for JEP Authors <http://www.jabber.org/jeps/jep-0143.html>." > -Roster Item Exchange JEP-0144: Roster Item Exchange <http://www.jabber.org/jeps/jep-0144.html>." > -Annotations JEP-0145: Annotations <http://www.jabber.org/jeps/jep-0145.html>." > -Remote Controlling Clients JEP-0146: Remote Controlling Clients <http://www.jabber.org/jeps/jep-0146.html>." > -XMPP URI Query Components JEP-0147: XMPP URI Query Components <http://www.jabber.org/jeps/jep-0147.html>." > -Instant Messaging Intelligence Quotient (IM IQ) JEP-0148: Instant Messaging Intelligence Quotient (IM IQ) <http://www.jabber.org/jeps/jep-0148.html>." > -Time Periods JEP-0149: Time Periods <http://www.jabber.org/jeps/jep-0149.html>." > -Use of Entity Tags in XMPP Extensions JEP-0150: Use of Entity Tags in XMPP Extensions <http://www.jabber.org/jeps/jep-0150.html>." > -Virtual Presence JEP-0151: Virtual Presence <http://www.jabber.org/jeps/jep-0151.html>." > -Reachability Addresses JEP-0152: Reachability Addresses <http://www.jabber.org/jeps/jep-0152.html>." > -vCard-Based Avatars JEP-0153: vCard-Based Avatars <http://www.jabber.org/jeps/jep-0153.html>." > -User Profile JEP-0154: User Profile <http://www.jabber.org/jeps/jep-0154.html>." > -Chat Session Negotiation JEP-0155: Chat Session Negotiation <http://www.jabber.org/jeps/jep-0155.html>." > -A DNS TXT Resource Record Format for XMPP Connection Methods JEP-0156: A DNS TXT Resource Record Format for XMPP Connection Methods <http://www.jabber.org/jeps/jep-0156.html>." > -Contact Addresses for XMPP Services JEP-0157: Contact Addresses for XMPP Services <http://www.jabber.org/jeps/jep-0157.html>." > -Robot Challenges JEP-0158: Robot Challenges <http://www.jabber.org/jeps/jep-0158.html>." > -SPIM-Blocking Control JEP-0159: SPIM-Blocking Control <http://www.jabber.org/jeps/jep-0159.html>." > -Best Practices for Handling Offline Messages JEP-0160: Best Practices for Handling Offline Messages <http://www.jabber.org/jeps/jep-0160.html>." > -SPIM Reporting JEP-0161: SPIM Reporting <http://www.jabber.org/jeps/jep-0161.html>." > -Best Practices for Roster and Subscription Management JEP-0162: Best Practices for Roster and Subscription Management <http://www.jabber.org/jeps/jep-0162.html>." > -Personal Eventing via Pubsub JEP-0163: Personal Eventing via Pubsub <http://www.jabber.org/jeps/jep-0163.html>." > -vCard Filtering JEP-0164: vCard Filtering <http://www.jabber.org/jeps/jep-0164.html>." > -Prevention of JID Spoofing JEP-0165: Prevention of JID Spoofing <http://www.jabber.org/jeps/jep-0165.html>." > -Jingle JEP-0166: Jingle <http://www.jabber.org/jeps/jep-0166.html>." > -Jingle Audio Content Description Format JEP-0167: Jingle Audio Content Description Format <http://www.jabber.org/jeps/jep-0167.html>." > -Resource Application Priority JEP-0168: Resource Application Priority <http://www.jabber.org/jeps/jep-0168.html>." > -Twas The Night Before Christmas (Jabber Version) JEP-0169: Twas The Night Before Christmas (Jabber Version) <http://www.jabber.org/jeps/jep-0169.html>." > -Recommended Order of Stream Feature Negotiation JEP-0170: Recommended Order of Stream Feature Negotiation <http://www.jabber.org/jeps/jep-0170.html>." > -Language Translation JEP-0171: Language Translation <http://www.jabber.org/jeps/jep-0171.html>." > -User Nickname JEP-0172: User Nickname <http://www.jabber.org/jeps/jep-0172.html>." > -Pubsub Subscription Storage JEP-0173: Pubsub Subscription Storage <http://www.jabber.org/jeps/jep-0173.html>." > -Link-Local Messaging JEP-0174: Link-Local Messaging <http://www.jabber.org/jeps/jep-0174.html>." > -Best Practices for Use of SASL ANONYMOUS JEP-0175: Best Practices for Use of SASL ANONYMOUS <http://www.jabber.org/jeps/jep-0175.html>." > -Jingle RTP-ICE Transport Method JEP-0176: Jingle RTP-ICE Transport Method <http://www.jabber.org/jeps/jep-0176.html>." > -Jingle Raw UDP Transport Method JEP-0177: Jingle Raw UDP Transport Method <http://www.jabber.org/jeps/jep-0177.html>." > -Best Practices for Use of SASL EXTERNAL JEP-0178: Best Practices for Use of SASL EXTERNAL <http://www.jabber.org/jeps/jep-0178.html>." > -Jingle IAX Transport Method JEP-0179: Jingle IAX Transport Method <http://www.jabber.org/jeps/jep-0179.html>." > -Jingle Video Content Description Format JEP-0180: Jingle Video Content Description Format <http://www.jabber.org/jeps/jep-0180.html>." > -Jingle DTMF JEP-0181: Jingle DTMF <http://www.jabber.org/jeps/jep-0181.html>." > -Application-Specific Error Conditions JEP-0182: Application-Specific Error Conditions <http://www.jabber.org/jeps/jep-0182.html>." > -Jingle Telepathy Transport Method JEP-0183: Jingle Telepathy Transport Method <http://www.jabber.org/jeps/jep-0183.html>." > -Message Receipts JEP-0184: Message Receipts <http://www.jabber.org/jeps/jep-0184.html>." > -Dialback Key Generation and Validation JEP-0185: Dialback Key Generation and Validation <http://www.jabber.org/jeps/jep-0185.html>." > -Invisible Command JEP-0186: Invisible Command <http://www.jabber.org/jeps/jep-0186.html>." > -Offline Encrypted Sessions JEP-0187: Offline Encrypted Sessions <http://www.jabber.org/jeps/jep-0187.html>." > -Cryptographic Design of Encrypted Sessions JEP-0188: Cryptographic Design of Encrypted Sessions <http://www.jabber.org/jeps/jep-0188.html>." > -Public Key Publishing JEP-0189: Public Key Publishing <http://www.jabber.org/jeps/jep-0189.html>." > -Best Practice for Closing Idle Streams JEP-0190: Best Practice for Closing Idle Streams <http://www.jabber.org/jeps/jep-0190.html>." > -Simple Communications Blocking JEP-0191: Simple Communications Blocking <http://www.jabber.org/jeps/jep-0191.html>." > -Proposed Stream Feature Improvements JEP-0192: Proposed Stream Feature Improvements <http://www.jabber.org/jeps/jep-0192.html>." > -Proposed Resource Binding Improvements JEP-0193: Proposed Resource Binding Improvements <http://www.jabber.org/jeps/jep-0193.html>." > -User Chatting JEP-0194: User Chatting <http://www.jabber.org/jeps/jep-0194.html>." > -User Browsing JEP-0195: User Browsing <http://www.jabber.org/jeps/jep-0195.html>." > -User Gaming JEP-0196: User Gaming <http://www.jabber.org/jeps/jep-0196.html>." > -User Viewing JEP-0197: User Viewing <http://www.jabber.org/jeps/jep-0197.html>." > +XMPP Extension Protocols XEP-0001: XMPP Extension Protocols <http://www.xmpp.org/extensions/xep-0001.html>." > +Jabber Interest Groups XEP-0002: Jabber Interest Groups <http://www.xmpp.org/extensions/xep-0002.html>." > +Proxy Accept Socket Service XEP-0002: Proxy Accept Socket Service <http://www.xmpp.org/extensions/xep-0003.html>." > +Data Forms XEP-0004: Data Forms <http://www.xmpp.org/extensions/xep-0004.html>." > +IQ-Based Avatars XEP-0008: IQ-Based Avatars <http://www.xmpp.org/extensions/xep-0008.html>." > +Jabber-RPC XEP-0009: Jabber-RPC <http://www.xmpp.org/extensions/xep-0009.html>." > +Jabber Browsing XEP-0011: Jabber Browsing <http://www.xmpp.org/extensions/xep-0011.html>." > +Last Activity XEP-0012: Last Activity <http://www.xmpp.org/extensions/xep-0012.html>." > +Flexible Offline Message Retrieval XEP-0013: Flexible Offline Message Retrieval <http://www.xmpp.org/extensions/xep-0013.html>." > + + +Server-Based Privacy Rules XEP-0016: Server-Based Privacy Rules <http://www.xmpp.org/extensions/xep-0016.html>." > + +Invisible Presence XEP-0018: Invisible Presence <http://www.xmpp.org/extensions/xep-0018.html>." > +Streamlining the JIGs XEP-0019: Streamlining the JIGs <http://www.xmpp.org/extensions/xep-0019.html>." > +Feature Negotiation XEP-0020: Feature Negotiation <http://www.xmpp.org/extensions/xep-0020.html>." > +Jabber Event Notification Service XEP-0021: Jabber Event Notification Service <http://www.xmpp.org/extensions/xep-0021.html>." > +Message Events XEP-0022: Message Events <http://www.xmpp.org/extensions/xep-0022.html>." > +Message Expiration XEP-0023: Message Expiration <http://www.xmpp.org/extensions/xep-0023.html>." > +Publish/Subscribe XEP-0024: Publish/Subscribe <http://www.xmpp.org/extensions/xep-0024.html>." > +Jabber HTTP Polling XEP-0025: Jabber HTTP Polling <http://www.xmpp.org/extensions/xep-0025.html>." > +Internationalization XEP-0026: Internationalization <http://www.xmpp.org/extensions/xep-0026.html>." > +Current Jabber OpenPGP Usage XEP-0027: Current Jabber OpenPGP Usage <http://www.xmpp.org/extensions/xep-0027.html>." > + +Definition of Jabber Identifiers XEP-0029: Definition of Jabber Identifiers <http://www.xmpp.org/extensions/xep-0029.html>." > +Service Discovery XEP-0030: Service Discovery <http://www.xmpp.org/extensions/xep-0030.html>." > +A Framework for Securing Jabber Conversations XEP-0031: A Framework for Securing Jabber Conversations <http://www.xmpp.org/extensions/xep-0031.html>." > +Jabber URI Scheme XEP-0032: Jabber URI Scheme <http://www.xmpp.org/extensions/xep-0032.html>." > +Extended Stanza Addressing XEP-0033: Extended Stanza Addressing <http://www.xmpp.org/extensions/xep-0033.html>." > +SASL Integration XEP-0034: SASL Integration <http://www.xmpp.org/extensions/xep-0034.html>." > +SSL/TLS Integration XEP-0035: SSL/TLS Integration <http://www.xmpp.org/extensions/xep-0035.html>." > +Pub-sub Subscriptions XEP-0036: Pub-sub Subscriptions <http://www.xmpp.org/extensions/xep-0036.html>." > + +Icon Styles XEP-0038: Icon Styles <http://www.xmpp.org/extensions/xep-0038.html>." > +Statistics Gathering XEP-0039: Statistics Gathering <http://www.xmpp.org/extensions/xep-0039.html>." > +Robust Publish-Subscribe XEP-0040: Robust Publish-Subscribe <http://www.xmpp.org/extensions/xep-0040.html>." > +Jidlink XEP-0041: Jidlink <http://www.xmpp.org/extensions/xep-0041.html>." > +Jabber OOB Broadcast Service XEP-0042: Jabber OOB Broadcast Service <http://www.xmpp.org/extensions/xep-0042.html>." > +Jabber Database Access XEP-0043: Jabber Database Access <http://www.xmpp.org/extensions/xep-0043.html>." > +Full Namespace Support in XML Streams XEP-0044: Full Namespace Support in XML Streams <http://www.xmpp.org/extensions/xep-0044.html>." > +Multi-User Chat XEP-0045: Multi-User Chat <http://www.xmpp.org/extensions/xep-0045.html>." > +Direct TCP XEP-0046: Direct TCP <http://www.xmpp.org/extensions/xep-0046.html>." > +In-Band Bytestreams XEP-0047: In-Band Bytestreams <http://www.xmpp.org/extensions/xep-0047.html>." > +Bookmark Storage XEP-0048: Bookmark Storage <http://www.xmpp.org/extensions/xep-0048.html>." > +Private XML Storage XEP-0049: Private XML Storage <http://www.xmpp.org/extensions/xep-0049.html>." > +Ad-Hoc Commands XEP-0050: Ad-Hoc Commands <http://www.xmpp.org/extensions/xep-0050.html>." > +Redirect and Connection Transfer XEP-0051: Redirect and Connection Transfer <http://www.xmpp.org/extensions/xep-0051.html>." > +File Transfer XEP-0052: File Transfer <http://www.xmpp.org/extensions/xep-0052.html>." > +XMPP Registrar XEP-0053: XMPP Registrar <http://www.xmpp.org/extensions/xep-0053.html>." > +vcard-temp XEP-0054: vcard-temp <http://www.xmpp.org/extensions/xep-0054.html>." > +Jabber Search XEP-0055: Jabber Search <http://www.xmpp.org/extensions/xep-0055.html>." > +Business Data Interchange XEP-0056: Business Data Interchange <http://www.xmpp.org/extensions/xep-0056.html>." > +Extended Roster XEP-0057: Extended Roster <http://www.xmpp.org/extensions/xep-0057.html>." > +Multi-User Text Editing XEP-0058: Multi-User Text Editing <http://www.xmpp.org/extensions/xep-0058.html>." > +Result Set Management XEP-0059: Result Set Management <http://www.xmpp.org/extensions/xep-0059.html>." > +Publish-Subscribe XEP-0060: Publish-Subscribe <http://www.xmpp.org/extensions/xep-0060.html>." > +Shared Notes XEP-0061: Shared Notes <http://www.xmpp.org/extensions/xep-0061.html>." > +Packet Filtering XEP-0062: Packet Filtering <http://www.xmpp.org/extensions/xep-0062.html>." > +Basic Filtering Operations XEP-0063: Basic Filtering Operations <http://www.xmpp.org/extensions/xep-0063.html>." > +XPath Filtering XEP-0064: XPath Filtering <http://www.xmpp.org/extensions/xep-0064.html>." > +SOCKS5 Bytestreams XEP-0065: SOCKS5 Bytestreams <http://www.xmpp.org/extensions/xep-0065.html>." > +Out-of-Band Data XEP-0066: Out of Band Data <http://www.xmpp.org/extensions/xep-0066.html>." > +Stock Data Transmission XEP-0067: Stock Data Transmission <http://www.xmpp.org/extensions/xep-0067.html>." > +Field Standardization for Data Forms XEP-0068: Field Data Standardization for Data Forms <http://www.xmpp.org/extensions/xep-0068.html>." > +Compliance JIG XEP-0069: Compliance JIG <http://www.xmpp.org/extensions/xep-0069.html>." > +Verifying HTTP Requests via XMPP XEP-0070: Verifying HTTP Requests via XMPP <http://www.xmpp.org/extensions/xep-0070.html>." > +XHTML-IM XEP-0071: XHTML-IM <http://www.xmpp.org/extensions/xep-0071.html>." > +SOAP over XMPP XEP-0072: SOAP over XMPP <http://www.xmpp.org/extensions/xep-0072.html>." > +Basic IM Protocol Suite XEP-0073: Basic IM Protocol Suite <http://www.xmpp.org/extensions/xep-0073.html>." > +Simple Access Control XEP-0074: Simple Access Control <http://www.xmpp.org/extensions/xep-0074.html>." > +Jabber Object Access Protocol XEP-0075: Jabber Object Access Protocol <http://www.xmpp.org/extensions/xep-0075.html>." > +Malicious Stanzas XEP-0076: Malicious Stanzas <http://www.xmpp.org/extensions/xep-0076.html>." > +In-Band Registration XEP-0077: In-Band Registration <http://www.xmpp.org/extensions/xep-0077.html>." > +Non-SASL Authentication XEP-0078: Non-SASL Authentication <http://www.xmpp.org/extensions/xep-0078.html>." > +Advanced Message Processing XEP-0079: Advanced Message Processing <http://www.xmpp.org/extensions/xep-0079.html>." > +User Geolocation XEP-0080: User Geolocation <http://www.xmpp.org/extensions/xep-0080.html>." > +Jabber MIME Type XEP-0081: Jabber MIME Type <http://www.xmpp.org/extensions/xep-0081.html>." > +Jabber Date and Time Profiles XEP-0082: Jabber Date and Time Profiles <http://www.xmpp.org/extensions/xep-0082.html>." > +Nested Roster Groups XEP-0083: Nested Roster Groups <http://www.xmpp.org/extensions/xep-0083.html>." > +User Avatar XEP-0084: User Avatar <http://www.xmpp.org/extensions/xep-0084.html>." > +Chat State Notifications XEP-0085: Chat State Notifications <http://www.xmpp.org/extensions/xep-0085.html>." > +Error Condition Mappings XEP-0086: Error Condition Mappings <http://www.xmpp.org/extensions/xep-0086.html>." > +Stream Initiation XEP-0087: Stream Initiation <http://www.xmpp.org/extensions/xep-0087.html>." > +Client Webtabs XEP-0088: Client Webtabs <http://www.xmpp.org/extensions/xep-0088.html>." > +Generic Alerts XEP-0089: Generic Alerts <http://www.xmpp.org/extensions/xep-0089.html>." > +Entity Time XEP-0090: Entity Time <http://www.xmpp.org/extensions/xep-0090.html>." > +Delayed Delivery XEP-0091: Delayed Delivery <http://www.xmpp.org/extensions/xep-0091.html>." > +Software Version XEP-0092: Software Version <http://www.xmpp.org/extensions/xep-0092.html>." > +Roster Item Exchange XEP-0093: Roster Item Exchange <http://www.xmpp.org/extensions/xep-0093.html>." > +Agent Information XEP-0094: Agent Information <http://www.xmpp.org/extensions/xep-0094.html>." > +Stream Initiation XEP-0095: Stream Initiation <http://www.xmpp.org/extensions/xep-0095.html>." > +File Transfer XEP-0096: File Transfer <http://www.xmpp.org/extensions/xep-0096.html>." > +iCal Envelope XEP-0097: iCal Envelope <http://www.xmpp.org/extensions/xep-0097.html>." > +Enchanced Private XML Storage XEP-0098: Enchanced Private XML Storage <http://www.xmpp.org/extensions/xep-0098.html>." > +IQ Query Action Protocol XEP-0099: IQ Query Action Protocol <http://www.xmpp.org/extensions/xep-0099.html>." > +Gateway Interaction XEP-0100: Gateway Interaction <http://www.xmpp.org/extensions/xep-0100.html>." > +HTTP Authentication using Jabber Tickets XEP-0101: HTTP Authentication using Jabber Tickets <http://www.xmpp.org/extensions/xep-0101.html>." > +Security Extensions XEP-0102: Security Extensions <http://www.xmpp.org/extensions/xep-0102.html>." > +URL Address Information XEP-0103: URL Address Information <http://www.xmpp.org/extensions/xep-0103.html>." > +HTTP Scheme for URL Data XEP-0104: HTTP Scheme for URL Data <http://www.xmpp.org/extensions/xep-0104.html>." > +Tree Transfer Stream Initiation Profile XEP-0105: Tree Transfer Stream Initiation Profile <http://www.xmpp.org/extensions/xep-0105.html>." > +JID Escaping XEP-0106: JID Escaping <http://www.xmpp.org/extensions/xep-0106.html>." > +User Mood XEP-0107: User Mood <http://www.xmpp.org/extensions/xep-0107.html>." > +User Activity XEP-0108: User Activity <http://www.xmpp.org/extensions/xep-0108.html>." > +Vacation Messages XEP-0109: Vacation Messages <http://www.xmpp.org/extensions/xep-0109.html>." > +Generic Maps XEP-0110: Generic Maps <http://www.xmpp.org/extensions/xep-0110.html>." > +A Transport for Initiating and Negotiating Sessions XEP-0111: A Transport for Initiating and Negotiating Sessions <http://www.xmpp.org/extensions/xep-0111.html>." > +User Physical Location XEP-0112: User Physical Location <http://www.xmpp.org/extensions/xep-0112.html>." > +Simple Whiteboarding XEP-0113: Simple Whiteboarding <http://www.xmpp.org/extensions/xep-0113.html>." > +Jabber Component Protocol XEP-0114: Jabber Component Protocol <http://www.xmpp.org/extensions/xep-0114.html>." > +Entity Capabilities XEP-0115: Entity Capabilities <http://www.xmpp.org/extensions/xep-0115.html>." > +Encrypted Sessions XEP-0116: Encrypted Sessions <http://www.xmpp.org/extensions/xep-0116.html>." > +Intermediate IM Protocol Suite XEP-0117: Intermediate IM Protocol Suite <http://www.xmpp.org/extensions/xep-0117.html>." > +User Tune XEP-0118: User Tune <http://www.xmpp.org/extensions/xep-0118.html>." > +Extended Presence Protocol Suite XEP-0119: Extended Presence Protocol Suite <http://www.xmpp.org/extensions/xep-0119.html>." > +Infobits XEP-0120: Infobits <http://www.xmpp.org/extensions/xep-0120.html>." > +Dublin Core Infobits Mapping XEP-0121: Dublin Core Infobits Mapping <http://www.xmpp.org/extensions/xep-0121.html>." > +Data Forms Validation XEP-0122: Data Forms Validation <http://www.xmpp.org/extensions/xep-0122.html>." > +Entity Metadata XEP-0123: Entity Metadata <http://www.xmpp.org/extensions/xep-0123.html>." > +HTTP Binding XEP-0124: HTTP Binding <http://www.xmpp.org/extensions/xep-0124.html>." > +vCard Infobits Mapping XEP-0125: vCard Infobits Mapping <http://www.xmpp.org/extensions/xep-0125.html>." > +Invisibility XEP-0126: Invisibility <http://www.xmpp.org/extensions/xep-0126.html>." > +Common Alerting Protocol (CAP) over XMPP XEP-0127: Common Alerting Protocol (CAP) over XMPP <http://www.xmpp.org/extensions/xep-0127.html>." > +Service Discovery Extensions XEP-0128: Service Discovery Extensions <http://www.xmpp.org/extensions/xep-0128.html>." > +WebDAV File Transfers XEP-0129: WebDAV File Transfers <http://www.xmpp.org/extensions/xep-0129.html>." > +Waiting Lists XEP-0130: Waiting Lists <http://www.xmpp.org/extensions/xep-0130.html>." > +Stanza Headers and Internet Metadata XEP-0131: Stanza Headers and Internet Metadata <http://www.xmpp.org/extensions/xep-0131.html>." > +Presence Obtained via Kinesthetic Excitation (POKE) XEP-0132: Presence Obtained via Kinesthetic Excitation (POKE) <http://www.xmpp.org/extensions/xep-0132.html>." > +Service Administration XEP-0133: Service Administration <http://www.xmpp.org/extensions/xep-0133.html>." > +Protocol Design Guidelines XEP-0134: Protocol Design Guidelines <http://www.xmpp.org/extensions/xep-0134.html>." > +File Sharing XEP-0135: File Sharing <http://www.xmpp.org/extensions/xep-0135.html>." > +Message Archiving XEP-0136: Message Archiving <http://www.xmpp.org/extensions/xep-0136.html>." > +Publishing Stream Initiation Requests XEP-0137: Publishing Stream Initiation Requests <http://www.xmpp.org/extensions/xep-0137.html>." > +Stream Compression XEP-0138: Stream Compression <http://www.xmpp.org/extensions/xep-0138.html>." > +Security JIG XEP-0139: Security JIG <http://www.xmpp.org/extensions/xep-0139.html>." > +Shared Groups XEP-0140: Shared Groups <http://www.xmpp.org/extensions/xep-0140.html>." > +Data Forms Layout XEP-0141: Data Forms Layout <http://www.xmpp.org/extensions/xep-0141.html>." > +Workgroup Queues XEP-0142: Workgroup Queues <http://www.xmpp.org/extensions/xep-0142.html>." > +Guidelines for Authors of XMPP Extension Protocols XEP-0143: Guidelines for Authors of XMPP Extension Protocols <http://www.xmpp.org/extensions/xep-0143.html>." > +Roster Item Exchange XEP-0144: Roster Item Exchange <http://www.xmpp.org/extensions/xep-0144.html>." > +Annotations XEP-0145: Annotations <http://www.xmpp.org/extensions/xep-0145.html>." > +Remote Controlling Clients XEP-0146: Remote Controlling Clients <http://www.xmpp.org/extensions/xep-0146.html>." > +XMPP URI Query Components XEP-0147: XMPP URI Query Components <http://www.xmpp.org/extensions/xep-0147.html>." > +Instant Messaging Intelligence Quotient (IM IQ) XEP-0148: Instant Messaging Intelligence Quotient (IM IQ) <http://www.xmpp.org/extensions/xep-0148.html>." > +Time Periods XEP-0149: Time Periods <http://www.xmpp.org/extensions/xep-0149.html>." > +Use of Entity Tags in XMPP Extensions XEP-0150: Use of Entity Tags in XMPP Extensions <http://www.xmpp.org/extensions/xep-0150.html>." > +Virtual Presence XEP-0151: Virtual Presence <http://www.xmpp.org/extensions/xep-0151.html>." > +Reachability Addresses XEP-0152: Reachability Addresses <http://www.xmpp.org/extensions/xep-0152.html>." > +vCard-Based Avatars XEP-0153: vCard-Based Avatars <http://www.xmpp.org/extensions/xep-0153.html>." > +User Profile XEP-0154: User Profile <http://www.xmpp.org/extensions/xep-0154.html>." > +Chat Session Negotiation XEP-0155: Chat Session Negotiation <http://www.xmpp.org/extensions/xep-0155.html>." > +A DNS TXT Resource Record Format for XMPP Connection Methods XEP-0156: A DNS TXT Resource Record Format for XMPP Connection Methods <http://www.xmpp.org/extensions/xep-0156.html>." > +Contact Addresses for XMPP Services XEP-0157: Contact Addresses for XMPP Services <http://www.xmpp.org/extensions/xep-0157.html>." > +Robot Challenges XEP-0158: Robot Challenges <http://www.xmpp.org/extensions/xep-0158.html>." > +SPIM-Blocking Control XEP-0159: SPIM-Blocking Control <http://www.xmpp.org/extensions/xep-0159.html>." > +Best Practices for Handling Offline Messages XEP-0160: Best Practices for Handling Offline Messages <http://www.xmpp.org/extensions/xep-0160.html>." > +SPIM Reporting XEP-0161: SPIM Reporting <http://www.xmpp.org/extensions/xep-0161.html>." > +Best Practices for Roster and Subscription Management XEP-0162: Best Practices for Roster and Subscription Management <http://www.xmpp.org/extensions/xep-0162.html>." > +Personal Eventing via Pubsub XEP-0163: Personal Eventing via Pubsub <http://www.xmpp.org/extensions/xep-0163.html>." > +vCard Filtering XEP-0164: vCard Filtering <http://www.xmpp.org/extensions/xep-0164.html>." > +Prevention of JID Spoofing XEP-0165: Prevention of JID Spoofing <http://www.xmpp.org/extensions/xep-0165.html>." > +Jingle XEP-0166: Jingle <http://www.xmpp.org/extensions/xep-0166.html>." > +Jingle Audio Content Description Format XEP-0167: Jingle Audio Content Description Format <http://www.xmpp.org/extensions/xep-0167.html>." > +Resource Application Priority XEP-0168: Resource Application Priority <http://www.xmpp.org/extensions/xep-0168.html>." > +Twas The Night Before Christmas (Jabber Version) XEP-0169: Twas The Night Before Christmas (Jabber Version) <http://www.xmpp.org/extensions/xep-0169.html>." > +Recommended Order of Stream Feature Negotiation XEP-0170: Recommended Order of Stream Feature Negotiation <http://www.xmpp.org/extensions/xep-0170.html>." > +Language Translation XEP-0171: Language Translation <http://www.xmpp.org/extensions/xep-0171.html>." > +User Nickname XEP-0172: User Nickname <http://www.xmpp.org/extensions/xep-0172.html>." > +Pubsub Subscription Storage XEP-0173: Pubsub Subscription Storage <http://www.xmpp.org/extensions/xep-0173.html>." > +Link-Local Messaging XEP-0174: Link-Local Messaging <http://www.xmpp.org/extensions/xep-0174.html>." > +Best Practices for Use of SASL ANONYMOUS XEP-0175: Best Practices for Use of SASL ANONYMOUS <http://www.xmpp.org/extensions/xep-0175.html>." > +Jingle RTP-ICE Transport Method XEP-0176: Jingle RTP-ICE Transport Method <http://www.xmpp.org/extensions/xep-0176.html>." > +Jingle Raw UDP Transport Method XEP-0177: Jingle Raw UDP Transport Method <http://www.xmpp.org/extensions/xep-0177.html>." > +Best Practices for Use of SASL EXTERNAL XEP-0178: Best Practices for Use of SASL EXTERNAL <http://www.xmpp.org/extensions/xep-0178.html>." > +Jingle IAX Transport Method XEP-0179: Jingle IAX Transport Method <http://www.xmpp.org/extensions/xep-0179.html>." > +Jingle Video Content Description Format XEP-0180: Jingle Video Content Description Format <http://www.xmpp.org/extensions/xep-0180.html>." > +Jingle DTMF XEP-0181: Jingle DTMF <http://www.xmpp.org/extensions/xep-0181.html>." > +Application-Specific Error Conditions XEP-0182: Application-Specific Error Conditions <http://www.xmpp.org/extensions/xep-0182.html>." > +Jingle Telepathy Transport Method XEP-0183: Jingle Telepathy Transport Method <http://www.xmpp.org/extensions/xep-0183.html>." > +Message Receipts XEP-0184: Message Receipts <http://www.xmpp.org/extensions/xep-0184.html>." > +Dialback Key Generation and Validation XEP-0185: Dialback Key Generation and Validation <http://www.xmpp.org/extensions/xep-0185.html>." > +Invisible Command XEP-0186: Invisible Command <http://www.xmpp.org/extensions/xep-0186.html>." > +Offline Encrypted Sessions XEP-0187: Offline Encrypted Sessions <http://www.xmpp.org/extensions/xep-0187.html>." > +Cryptographic Design of Encrypted Sessions XEP-0188: Cryptographic Design of Encrypted Sessions <http://www.xmpp.org/extensions/xep-0188.html>." > +Public Key Publishing XEP-0189: Public Key Publishing <http://www.xmpp.org/extensions/xep-0189.html>." > +Best Practice for Closing Idle Streams XEP-0190: Best Practice for Closing Idle Streams <http://www.xmpp.org/extensions/xep-0190.html>." > +Simple Communications Blocking XEP-0191: Simple Communications Blocking <http://www.xmpp.org/extensions/xep-0191.html>." > +Proposed Stream Feature Improvements XEP-0192: Proposed Stream Feature Improvements <http://www.xmpp.org/extensions/xep-0192.html>." > +Proposed Resource Binding Improvements XEP-0193: Proposed Resource Binding Improvements <http://www.xmpp.org/extensions/xep-0193.html>." > +User Chatting XEP-0194: User Chatting <http://www.xmpp.org/extensions/xep-0194.html>." > +User Browsing XEP-0195: User Browsing <http://www.xmpp.org/extensions/xep-0195.html>." > +User Gaming XEP-0196: User Gaming <http://www.xmpp.org/extensions/xep-0196.html>." > +User Viewing XEP-0197: User Viewing <http://www.xmpp.org/extensions/xep-0197.html>." > diff --git a/xep.xsd b/xep.xsd index 6865ef1a..747d6643 100644 --- a/xep.xsd +++ b/xep.xsd @@ -2,22 +2,22 @@ - + - This schema defines the document format for Jabber Enhancement - Proposals (JEPs). For further information about JEPs, visit: + This schema defines the document format for XMPP Extension + Protocols (XEPs). For further information about XEPs, visit: - http://www.jabber.org/jeps/ + http://www.xmpp.org/extensions/ The canonical URL for this schema is: - http://www.jabber.org/jeps/jep.xsd + http://www.xmpp.org/extensions/xep.xsd @@ -64,7 +64,7 @@ - + diff --git a/xep.xsl b/xep.xsl index f95391ba..304ee458 100644 --- a/xep.xsl +++ b/xep.xsl @@ -8,18 +8,18 @@ - JEP-<xsl:value-of select='/jep/header/number'/>:<xsl:text> </xsl:text><xsl:value-of select='/jep/header/title' /> + XEP-<xsl:value-of select='/xep/header/number'/>:<xsl:text> </xsl:text><xsl:value-of select='/xep/header/title' /> DC.Title - + - + DC.Description - + DC.Publisher @@ -27,15 +27,15 @@ DC.Contributor - JEP Editor + XMPP Extensions Editor DC.Date - + DC.Type - Jabber Enhancement Proposal + XMPP Extension Protocol DC.Format @@ -43,7 +43,7 @@ DC.Identifier - JEP- + XEP- DC.Language @@ -51,108 +51,108 @@ DC.Rights - + -

      JEP-:

      +

      XEP-:

      -

      +

      - - + + -

      NOTICE: This Historical JEP provides canonical documentation of a protocol that is in use within the Jabber/XMPP community. This JEP is not a standards-track specification within the Jabber Software Foundation's standards process; however, it may be converted to standards-track in the future or may be obsoleted by a more modern protocol.

      +

      NOTICE: This Historical specification provides canonical documentation of a protocol that is in use within the Jabber/XMPP community. This document is not a standards-track specification within the Jabber Software Foundation's standards process; however, it may be converted to standards-track in the future or may be obsoleted by a more modern protocol.

       -

      NOTICE: This JEP is Humorous. It MAY provide amusement but SHOULD NOT be taken seriously.

      +

      NOTICE: This document is Humorous. It MAY provide amusement but SHOULD NOT be taken seriously.

       -

      NOTICE: This Informational JEP defines a best practice or protocol profile that has been approved by the Jabber Council and/or the JSF Board of Directors. Implementations are encouraged and the best practice or protocol profile is appropriate for deployment in production systems.

      +

      NOTICE: This Informational specification defines a best practice or protocol profile that has been approved by the XMPP Council and/or the JSF Board of Directors. Implementations are encouraged and the best practice or protocol profile is appropriate for deployment in production systems.

       -

      NOTICE: This Procedural JEP defines a process or activity of the Jabber Software Foundation (JSF) that has been approved by the Jabber Council and/or the JSF Board of Directors. The JSF is currently following the process or activity defined herein and will do so until this JEP is deprecated or obsoleted.

      +

      NOTICE: This Procedural document defines a process or activity of the Jabber Software Foundation (JSF) that has been approved by the XMPP Council and/or the JSF Board of Directors. The JSF is currently following the process or activity defined herein and will do so until this document is deprecated or obsoleted.

       -

      WARNING: Consideration of this JEP has been Deferred by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended.

      +

      WARNING: Consideration of this document has been Deferred by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended.

       -

      WARNING: This JEP has been deprecated by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

      +

      WARNING: This document has been deprecated by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

      NOTICE: The protocol defined herein is a Draft Standard of the Jabber Software Foundation. Implementations are encouraged and the protocol is appropriate for deployment in production systems, but some changes to the protocol are possible before it becomes a Final Standard.

       -

      NOTICE: This Historical JEP attempts to provide canonical documentation of a protocol that is in use within the Jabber/XMPP community. Publication as a Jabber Enhancement Proposal does not imply approval of this proposal by the Jabber Software Foundation. This JEP is not a standards-track specification within the Jabber Software Foundation's standards process; however, it may be converted to standards-track in the future or may be obsoleted by a more modern protocol.

      +

      NOTICE: This Historical document attempts to provide canonical documentation of a protocol that is in use within the Jabber/XMPP community. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the Jabber Software Foundation. This document is not a standards-track specification within the Jabber Software Foundation's standards process; however, it may be converted to standards-track in the future or may be obsoleted by a more modern protocol.

       -

      WARNING: This Informational JEP is Experimental. Publication as a Jabber Enhancement Proposal does not imply approval of this proposal by the Jabber Software Foundation. Implementation of the best practice or protocol profile described herein is encouraged in exploratory implementations, although production systems should not deploy implementations of this protocol until it advances to a status of Draft.

      +

      WARNING: This Informational document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the Jabber Software Foundation. Implementation of the best practice or protocol profile described herein is encouraged in exploratory implementations, although production systems should not deploy implementations of this protocol until it advances to a status of Draft.

       -

      NOTICE: This Procedural JEP proposes that the process or activity defined herein shall be followed by the Jabber Software Foundation (JSF). However, this process or activity has not yet been approved by the Jabber Council and/or the JSF Board of Directors and is therefore not currently in force.

      +

      NOTICE: This Procedural document proposes that the process or activity defined herein shall be followed by the Jabber Software Foundation (JSF). However, this process or activity has not yet been approved by the XMPP Council and/or the JSF Board of Directors and is therefore not currently in force.

       -

      WARNING: This Standards-Track JEP is Experimental. Publication as a Jabber Enhancement Proposal does not imply approval of this proposal by the Jabber Software Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems should not deploy implementations of this protocol until it advances to a status of Draft.

      +

      WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the Jabber Software Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems should not deploy implementations of this protocol until it advances to a status of Draft.

      NOTICE: The protocol defined herein is a Final Standard of the Jabber Software Foundation and may be considered a stable technology for implementation and deployment.

       -

      WARNING: This JEP has been obsoleted by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

      +

      WARNING: This document has been obsoleted by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

       -

      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.

      +

      NOTICE: This document is currently within Last Call or under consideration by the XMPP Council for advancement to the next stage in the JSF standards process.

       - -

      WARNING: This document has not yet been accepted for consideration or approved in any official manner by the Jabber Software Foundation, and this document must not be referred to as a Jabber Enhancement Proposal (JEP). If this document is accepted as a JEP by the Jabber Council, it will be published at <http://www.jabber.org/jeps/> and announced on the <standards-jig@jabber.org> mailing list.

      + +

      WARNING: This document has not yet been accepted for consideration or approved in any official manner by the Jabber Software Foundation, and this document must not be referred to as an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <http://www.xmpp.org/extensions/> and announced on the <standards-jig@jabber.org> mailing list.

       -

      WARNING: This JEP has been Rejected by the Jabber Council. Implementation of the protocol described herein is not recommended under any circumstances.

      +

      WARNING: This document has been Rejected by the XMPP Council. Implementation of the protocol described herein is not recommended under any circumstances.

       -

      WARNING: This JEP has been retracted by the author(s). Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

      +

      WARNING: This document has been retracted by the author(s). Implementation of the protocol described herein is not recommended. Developers desiring similar functionality should implement the protocol that supersedes this one (if any).

      - -

      JEP Information

      + +

      XEP Information

      Status: - http://www.jabber.org/jeps/jep-0001.html#states- - + http://www.xmpp.org/extensions/xep-0001.html#states- +
      Type: - http://www.jabber.org/jeps/jep-0001.html#types- - + http://www.xmpp.org/extensions/xep-0001.html#types- +
      - Number:
      - Version:
      - Last Updated:
      - + Number:
      + Version:
      + Last Updated:
      + - Expires:
      + Expires:
      - JIG:
      - + JIG:
      + Approving Body: JSF Board of Directors
       - Approving Body: Jabber Council
      + Approving Body: XMPP Council
             - + Dependencies: - +
      @@ -161,11 +161,11 @@ Dependencies: None
       - + Supersedes: - +
      @@ -174,11 +174,11 @@ Supersedes: None
       - + Superseded By: - +
      @@ -187,17 +187,17 @@ Superseded By: None
       - Short Name:
      - + Short Name:
      + - + - + Registry: http://www.jabber.org/registrar/ - + .html <> @@ -205,25 +205,25 @@ http://wiki.jabber.org/index.php/ - - (JEP- - + + (XEP- + ) - + Wiki Page: <>

      Author Information

      - +
      - +

      Discussion Venue

      - +

      The preferred venue for discussion of this document is the Standards-JIG discussion list: <http://mail.jabber.org/mailman/listinfo/standards-jig>.

      @@ -231,25 +231,25 @@

      The preferred venue for discussion of this document is the Standards-JIG discussion list: <http://mail.jabber.org/mailman/listinfo/standards-jig>.

      - -

      Given that this JEP normatively references IETF technologies, discussion on the JSF-IETF list may also be appropriate (see <http://mail.jabber.org/mailman/listinfo/jsf-ietf> for details).

      + +

      Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the JSF-IETF list may also be appropriate (see <http://mail.jabber.org/mailman/listinfo/jsf-ietf> for details).

             - +

      Relation to XMPP

      -

      The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the Jabber Software Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this JEP has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

      +

      The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the Jabber Software Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

      Conformance Terms

      The following keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

      - +

      - +

      Notes

      @@ -260,7 +260,7 @@

      Revision History

      - +

      END