diff --git a/protopage.xsl b/protopage.xsl index d195c41f..5d0a6847 100644 --- a/protopage.xsl +++ b/protopage.xsl @@ -22,7 +22,7 @@ DC.Publisher - Jabber Software Foundation + XMPP Standards Foundation DC.Date @@ -41,7 +41,7 @@ XEP-: - (part of the XEP series published by the Jabber Software Foundation).

+ (part of the XEP series published by the XMPP Standards Foundation).

diff --git a/ref.xsl b/ref.xsl index ca0ced1f..3de98cb7 100644 --- a/ref.xsl +++ b/ref.xsl @@ -66,7 +66,7 @@ - JSF XEP + XSF XEP diff --git a/xep.dtd b/xep.dtd index a3fa1a98..ffa53edb 100644 --- a/xep.dtd +++ b/xep.dtd @@ -1,14 +1,14 @@ - + - + diff --git a/xep.ent b/xep.ent index 6ffb9e74..de1e0411 100644 --- a/xep.ent +++ b/xep.ent @@ -120,11 +120,11 @@ - + -This XMPP Extension Protocol is copyright 1999 - 2007 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/>)." > +This XMPP Extension Protocol is copyright 1999 - 2007 by the XMPP Standards Foundation (XSF) and is in full conformance with the XSF'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/>)." > - + Note: This document describes a protocol or best practice that is intended for incorporation into the specification that will supersede &rfc3920; within the Internet Standards Process, i.e., &rfc3920bis;. This document is provided only for the purpose of open community discussion of the potential modification and will be obsoleted as soon as the relevant RFC is published.

" > Note: This document describes a protocol or best practice that is intended for incorporation into the specification that will supersede &rfc3921; within the Internet Standards Process, i.e., &rfc3921bis;. This document is provided only for the purpose of open community discussion of the potential modification and will be obsoleted as soon as the relevant RFC is published.

" > @@ -137,17 +137,17 @@ The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in &rfc2119;.

' > - + -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>." > -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/>." > +XSF Board of Directors The XSF Board of Directors is an elected body that possesses overall responsibility for the affairs of the XMPP Standards Foundation. For further information, see <http://www.jabber.org/board/>." > +XSF Bylaws The Bylaws of the XMPP Standards Foundation (XSF) define the legal basis and operating procedures of the XSF. For further information, see <http://www.jabber.org/xsf/docs/bylaws.shtml>." > +XMPP Council The XMPP Council is a technical steering committee, authorized by the XSF Board of Directors and elected by XSF members, that approves of new XMPP Extensions Protocols and oversees the XSF'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 XSF Board of Directors to handle protocol submissions and provide day-to-day management of the XSF's standards process. For further information, see <http://www.xmpp.org/extensions/editor.shtml>." > +XMPP Standards Foundation (XSF) The XMPP Standards Foundation (XSF) is an independent, non-profit membership organization that develops open extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP). For further information, see <http://www.xmpp.org/xsf/>." > +XSF-IETF list The XSF-IETF list is for discussion of matters of mutual interest to the XMPP Standards Foundation and the Internet Engineering Task Force. The primary focus of the list is technical, mainly regarding XSF use of IETF technologies (e.g., references to RFCs in XMPP Extension Protocols) and IETF use of XSF 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/>." > +XSF IPR Policy The XSF IPR Policy defines the XMPP Standards 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 XMPP Standards Foundation. For further information, see <http://www.xmpp.org/registrar/>." > +Standards SIG The Standards SIG is a standing Special Interest Group devoted to development of XMPP Extension Protocols. The discussion list of the Standards SIG is the primary venue for discussion of XMPP protocol extensions, 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/>." > @@ -593,7 +593,7 @@ 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>." > +Streamlining the SIGs XEP-0019: Streamlining the SIGs <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>." > @@ -643,7 +643,7 @@ 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>." > +Compliance SIG XEP-0069: Compliance SIG <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>." > @@ -713,7 +713,7 @@ 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>." > +Security SIG XEP-0139: Security SIG <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>." > diff --git a/xep.xsd b/xep.xsd index 5747381c..734b74e8 100644 --- a/xep.xsd +++ b/xep.xsd @@ -38,7 +38,7 @@ - + diff --git a/xep.xsl b/xep.xsl index 1fe1e194..8f2ccb86 100644 --- a/xep.xsl +++ b/xep.xsl @@ -23,7 +23,7 @@ DC.Publisher - Jabber Software Foundation + XMPP Standards Foundation DC.Contributor @@ -65,49 +65,49 @@ -

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 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 XMPP Standards 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 document is Humorous. It MAY provide amusement but SHOULD NOT be taken seriously.

 -

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 Informational specification defines a best practice or protocol profile that has been approved by the XMPP Council and/or the XSF Board of Directors. Implementations are encouraged and the best practice or protocol profile is appropriate for deployment in production systems.

 -

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.

+

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

 -

WARNING: Consideration of this document 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 XMPP Standards Foundation. Implementation of the protocol described herein is not recommended.

 -

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

+

WARNING: This document has been deprecated by the XMPP Standards 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: The protocol defined herein is a Draft Standard of the XMPP Standards 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 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.

+

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 XMPP Standards Foundation. This document is not a standards-track specification within the XMPP Standards 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 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.

+

WARNING: This Informational document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards 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 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.

+

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

 -

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.

+

WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards 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.

+

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

 -

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

+

WARNING: This document has been obsoleted by the XMPP Standards 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 document is currently within Last Call or under consideration by the XMPP 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 XSF 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 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 document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards 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 document has been Rejected by the XMPP Council. Implementation of the protocol described herein is not recommended under any circumstances.

@@ -119,6 +119,9 @@

Document Information

+ Series: XEP
+ Number:
+ Publisher: XMPP Standards Foundation
Status: http://www.xmpp.org/extensions/xep-0001.html#states- @@ -131,21 +134,19 @@
- Number:
Version:
Last Updated:
Expires:
- Publishing Organization: Jabber Software Foundation
- Approving Body: JSF Board of Directors
+ Approving Body: XSF Board of Directors
 - Approving Body: XMPP Council
+ Approving Body: XMPP Council
 @@ -196,7 +197,7 @@ Registry: - http://www.jabber.org/registrar/ + http://www.xmpp.org/registrar/ .html @@ -226,13 +227,13 @@ -

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

-

Discussion by the membership of the JSF may also be appropriate (see <http://mail.jabber.org/mailman/listinfo/members> for details).

+

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

+

Discussion by the membership of the XSF may also be appropriate (see <http://mail.jabber.org/mailman/listinfo/members> for details).

-

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

+

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

-

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

+

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

 @@ -240,7 +241,7 @@

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

+

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the XMPP Standards 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".