git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@334 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-01-15 19:18:37 +00:00
parent 734732b3ba
commit f18ab40f93
6 changed files with 48 additions and 47 deletions

View File

@ -22,7 +22,7 @@
</meta>
<meta>
<xsl:attribute name='name'><xsl:text>DC.Publisher</xsl:text></xsl:attribute>
<xsl:attribute name='content'>Jabber Software Foundation</xsl:attribute>
<xsl:attribute name='content'>XMPP Standards Foundation</xsl:attribute>
</meta>
<meta>
<xsl:attribute name='name'><xsl:text>DC.Date</xsl:text></xsl:attribute>
@ -41,7 +41,7 @@
</xsl:attribute>
<xsl:text>XEP-</xsl:text><xsl:value-of select='/xep/header/number' />:<xsl:text> </xsl:text><xsl:value-of select='/xep/header/title' />
</a>
(part of the <a href="http://www.xmpp.org/extensions/">XEP series</a> published by the <a href="http://www.jabber.org/jsf/">Jabber Software Foundation</a>).</p>
(part of the <a href="http://www.xmpp.org/extensions/">XEP series</a> published by the <a href="http://www.xmpp.org/xsf/">XMPP Standards Foundation</a>).</p>
<xsl:variable name='schema.count' select='count(/xep/header/schemaloc)'/>
<xsl:if test='$schema.count &gt; 0'>

View File

@ -66,7 +66,7 @@
</date>
</front>
<seriesInfo>
<xsl:attribute name='name'><xsl:text>JSF XEP</xsl:text></xsl:attribute>
<xsl:attribute name='name'><xsl:text>XSF XEP</xsl:text></xsl:attribute>
<xsl:attribute name='value'><xsl:value-of select='/xep/header/number'/></xsl:attribute>
</seriesInfo>
<format>

View File

@ -1,14 +1,14 @@
<?xml version='1.0' encoding='UTF-8'?>
<!ELEMENT xep ( header, section1* ) >
<!ELEMENT header ( title, abstract, legal, number, status, type, jig, approver, dependencies, supersedes, supersededby, shortname, schemaloc*, registry?, expires?, author+, revision+ ) >
<!ELEMENT header ( title, abstract, legal, number, status, type, sig, approver, dependencies, supersedes, supersededby, shortname, schemaloc*, registry?, expires?, author+, revision+ ) >
<!ELEMENT title (#PCDATA)* >
<!ELEMENT abstract (#PCDATA)* >
<!ELEMENT legal (#PCDATA | link )* >
<!ELEMENT number (#PCDATA)* >
<!ELEMENT status (#PCDATA)* >
<!ELEMENT type (#PCDATA)* >
<!ELEMENT jig (#PCDATA)* >
<!ELEMENT sig (#PCDATA)* >
<!ELEMENT approver (#PCDATA)* >
<!ELEMENT dependencies ( spec* ) >
<!ELEMENT supersedes ( spec? ) >

32
xep.ent
View File

@ -120,11 +120,11 @@
<!-- no number for unexpected-request -->
<!ENTITY unexpected "&lt;unexpected-request/&gt;">
<!-- legal notice required by the JSF's IPR Policy -->
<!-- legal notice required by the XSF's IPR Policy -->
<!ENTITY LEGALNOTICE "<legal>This XMPP Extension Protocol is copyright 1999 - 2007 by the <link url='http://www.jabber.org/jsf/'>Jabber Software Foundation</link> (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt;. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (&lt;<link url='http://creativecommons.org/licenses/by/2.5/'>http://creativecommons.org/licenses/by/2.5/</link>&gt;).</legal>" >
<!ENTITY LEGALNOTICE "<legal>This XMPP Extension Protocol is copyright 1999 - 2007 by the <link url='http://www.xmpp.org/xsf/'>XMPP Standards Foundation</link> (XSF) and is in full conformance with the XSF's Intellectual Property Rights Policy &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt;. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (&lt;<link url='http://creativecommons.org/licenses/by/2.5/'>http://creativecommons.org/licenses/by/2.5/</link>&gt;).</legal>" >
<!-- other JSF-related text shortcuts -->
<!-- other XSF-related text shortcuts -->
<!ENTITY RFC3920BISNOTE "<p><em>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.</em></p>" >
<!ENTITY RFC3921BISNOTE "<p><em>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.</em></p>" >
@ -137,17 +137,17 @@
<!ENTITY CONFORMANCE '<p>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;.</p>' >
<!-- common JSF-related URLs -->
<!-- common XSF-related URLs -->
<!ENTITY BOARD "<span class='ref'>JSF Board of Directors</span> <note>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 &lt;<link url='http://www.jabber.org/board/'>http://www.jabber.org/board/</link>&gt;.</note>" >
<!ENTITY BYLAWS "<span class='ref'>JSF Bylaws</span> <note>The Bylaws of the Jabber Software Foundation (JSF) define the legal basis and operating procedures of the JSF. For further information, see &lt;<link url='http://www.jabber.org/jsf/bylaws.shtml'>http://www.jabber.org/jsf/bylaws.shtml</link>&gt;.</note>" >
<!ENTITY COUNCIL "<span class='ref'>XMPP Council</span> <note>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 &lt;<link url='http://www.xmpp.org/council/'>http://www.xmpp.org/council/</link>&gt;.</note>" >
<!ENTITY EDITOR "<span class='ref'>XMPP Extensions Editor</span> <note>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 &lt;<link url='http://www.xmpp.org/extensions/editor.shtml'>http://www.xmpp.org/extensions/editor.shtml</link>&gt;.</note>" >
<!ENTITY JSF "<span class='ref'>Jabber Software Foundation (JSF)</span> <note>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 &lt;<link url='http://www.jabber.org/jsf/'>http://www.jabber.org/jsf/</link>&gt;.</note>" >
<!ENTITY JSFIETF "<span class='ref'>JSF-IETF list</span> <note>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 &lt;<link url='http://mail.jabber.org/mailman/listinfo/jsf-ietf/'>http://mail.jabber.org/mailman/listinfo/jsf-ietf/</link>&gt;.</note>" >
<!ENTITY JSFIPR "<span class='ref'>JSF IPR Policy</span> <note>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 &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt;.</note>" >
<!ENTITY REGISTRAR "<span class='ref'>XMPP Registrar</span> <note>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 &lt;<link url='http://www.xmpp.org/registrar/'>http://www.xmpp.org/registrar/</link>&gt;.</note>" >
<!ENTITY SJIG "<span class='ref'>Standards JIG</span> <note>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 &lt;<link url='http://mail.jabber.org/mailman/listinfo/standards-jig/'>http://mail.jabber.org/mailman/listinfo/standards-jig/</link>&gt;.</note>" >
<!ENTITY BOARD "<span class='ref'>XSF Board of Directors</span> <note>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 &lt;<link url='http://www.jabber.org/board/'>http://www.jabber.org/board/</link>&gt;.</note>" >
<!ENTITY BYLAWS "<span class='ref'>XSF Bylaws</span> <note>The Bylaws of the XMPP Standards Foundation (XSF) define the legal basis and operating procedures of the XSF. For further information, see &lt;<link url='http://www.xmpp.org/xsf/docs/bylaws.shtml'>http://www.jabber.org/xsf/docs/bylaws.shtml</link>&gt;.</note>" >
<!ENTITY COUNCIL "<span class='ref'>XMPP Council</span> <note>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 &lt;<link url='http://www.xmpp.org/council/'>http://www.xmpp.org/council/</link>&gt;.</note>" >
<!ENTITY EDITOR "<span class='ref'>XMPP Extensions Editor</span> <note>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 &lt;<link url='http://www.xmpp.org/extensions/editor.shtml'>http://www.xmpp.org/extensions/editor.shtml</link>&gt;.</note>" >
<!ENTITY XSF "<span class='ref'>XMPP Standards Foundation (XSF)</span> <note>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 &lt;<link url='http://www.xmpp.org/xsf/'>http://www.xmpp.org/xsf/</link>&gt;.</note>" >
<!ENTITY XSFIETF "<span class='ref'>XSF-IETF list</span> <note>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 &lt;<link url='http://mail.jabber.org/mailman/listinfo/jsf-ietf/'>http://mail.jabber.org/mailman/listinfo/jsf-ietf/</link>&gt;.</note>" >
<!ENTITY XSFIPR "<span class='ref'>XSF IPR Policy</span> <note>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 &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt;.</note>" >
<!ENTITY REGISTRAR "<span class='ref'>XMPP Registrar</span> <note>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 &lt;<link url='http://www.xmpp.org/registrar/'>http://www.xmpp.org/registrar/</link>&gt;.</note>" >
<!ENTITY SSIG "<span class='ref'>Standards SIG</span> <note>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 &lt;<link url='http://mail.jabber.org/mailman/listinfo/standards-jig/'>http://mail.jabber.org/mailman/listinfo/standards-jig/</link>&gt;.</note>" >
<!-- various code projects -->
@ -593,7 +593,7 @@
<!ENTITY xep0016 "<span class='ref'>Server-Based Privacy Rules</span> <note>XEP-0016: Server-Based Privacy Rules &lt;<link url='http://www.xmpp.org/extensions/xep-0016.html'>http://www.xmpp.org/extensions/xep-0016.html</link>&gt;.</note>" >
<!-- XEP-0017 was rejected -->
<!ENTITY xep0018 "<span class='ref'>Invisible Presence</span> <note>XEP-0018: Invisible Presence &lt;<link url='http://www.xmpp.org/extensions/xep-0018.html'>http://www.xmpp.org/extensions/xep-0018.html</link>&gt;.</note>" >
<!ENTITY xep0019 "<span class='ref'>Streamlining the JIGs</span> <note>XEP-0019: Streamlining the JIGs &lt;<link url='http://www.xmpp.org/extensions/xep-0019.html'>http://www.xmpp.org/extensions/xep-0019.html</link>&gt;.</note>" >
<!ENTITY xep0019 "<span class='ref'>Streamlining the SIGs</span> <note>XEP-0019: Streamlining the SIGs &lt;<link url='http://www.xmpp.org/extensions/xep-0019.html'>http://www.xmpp.org/extensions/xep-0019.html</link>&gt;.</note>" >
<!ENTITY xep0020 "<span class='ref'>Feature Negotiation</span> <note>XEP-0020: Feature Negotiation &lt;<link url='http://www.xmpp.org/extensions/xep-0020.html'>http://www.xmpp.org/extensions/xep-0020.html</link>&gt;.</note>" >
<!ENTITY xep0021 "<span class='ref'>Jabber Event Notification Service</span> <note>XEP-0021: Jabber Event Notification Service &lt;<link url='http://www.xmpp.org/extensions/xep-0021.html'>http://www.xmpp.org/extensions/xep-0021.html</link>&gt;.</note>" >
<!ENTITY xep0022 "<span class='ref'>Message Events</span> <note>XEP-0022: Message Events &lt;<link url='http://www.xmpp.org/extensions/xep-0022.html'>http://www.xmpp.org/extensions/xep-0022.html</link>&gt;.</note>" >
@ -643,7 +643,7 @@
<!ENTITY xep0066 "<span class='ref'>Out-of-Band Data</span> <note>XEP-0066: Out of Band Data &lt;<link url='http://www.xmpp.org/extensions/xep-0066.html'>http://www.xmpp.org/extensions/xep-0066.html</link>&gt;.</note>" >
<!ENTITY xep0067 "<span class='ref'>Stock Data Transmission</span> <note>XEP-0067: Stock Data Transmission &lt;<link url='http://www.xmpp.org/extensions/xep-0067.html'>http://www.xmpp.org/extensions/xep-0067.html</link>&gt;.</note>" >
<!ENTITY xep0068 "<span class='ref'>Field Standardization for Data Forms</span> <note>XEP-0068: Field Data Standardization for Data Forms &lt;<link url='http://www.xmpp.org/extensions/xep-0068.html'>http://www.xmpp.org/extensions/xep-0068.html</link>&gt;.</note>" >
<!ENTITY xep0069 "<span class='ref'>Compliance JIG</span> <note>XEP-0069: Compliance JIG &lt;<link url='http://www.xmpp.org/extensions/xep-0069.html'>http://www.xmpp.org/extensions/xep-0069.html</link>&gt;.</note>" >
<!ENTITY xep0069 "<span class='ref'>Compliance SIG</span> <note>XEP-0069: Compliance SIG &lt;<link url='http://www.xmpp.org/extensions/xep-0069.html'>http://www.xmpp.org/extensions/xep-0069.html</link>&gt;.</note>" >
<!ENTITY xep0070 "<span class='ref'>Verifying HTTP Requests via XMPP</span> <note>XEP-0070: Verifying HTTP Requests via XMPP &lt;<link url='http://www.xmpp.org/extensions/xep-0070.html'>http://www.xmpp.org/extensions/xep-0070.html</link>&gt;.</note>" >
<!ENTITY xep0071 "<span class='ref'>XHTML-IM</span> <note>XEP-0071: XHTML-IM &lt;<link url='http://www.xmpp.org/extensions/xep-0071.html'>http://www.xmpp.org/extensions/xep-0071.html</link>&gt;.</note>" >
<!ENTITY xep0072 "<span class='ref'>SOAP over XMPP</span> <note>XEP-0072: SOAP over XMPP &lt;<link url='http://www.xmpp.org/extensions/xep-0072.html'>http://www.xmpp.org/extensions/xep-0072.html</link>&gt;.</note>" >
@ -713,7 +713,7 @@
<!ENTITY xep0136 "<span class='ref'>Message Archiving</span> <note>XEP-0136: Message Archiving &lt;<link url='http://www.xmpp.org/extensions/xep-0136.html'>http://www.xmpp.org/extensions/xep-0136.html</link>&gt;.</note>" >
<!ENTITY xep0137 "<span class='ref'>Publishing Stream Initiation Requests</span> <note>XEP-0137: Publishing Stream Initiation Requests &lt;<link url='http://www.xmpp.org/extensions/xep-0137.html'>http://www.xmpp.org/extensions/xep-0137.html</link>&gt;.</note>" >
<!ENTITY xep0138 "<span class='ref'>Stream Compression</span> <note>XEP-0138: Stream Compression &lt;<link url='http://www.xmpp.org/extensions/xep-0138.html'>http://www.xmpp.org/extensions/xep-0138.html</link>&gt;.</note>" >
<!ENTITY xep0139 "<span class='ref'>Security JIG</span> <note>XEP-0139: Security JIG &lt;<link url='http://www.xmpp.org/extensions/xep-0139.html'>http://www.xmpp.org/extensions/xep-0139.html</link>&gt;.</note>" >
<!ENTITY xep0139 "<span class='ref'>Security SIG</span> <note>XEP-0139: Security SIG &lt;<link url='http://www.xmpp.org/extensions/xep-0139.html'>http://www.xmpp.org/extensions/xep-0139.html</link>&gt;.</note>" >
<!ENTITY xep0140 "<span class='ref'>Shared Groups</span> <note>XEP-0140: Shared Groups &lt;<link url='http://www.xmpp.org/extensions/xep-0140.html'>http://www.xmpp.org/extensions/xep-0140.html</link>&gt;.</note>" >
<!ENTITY xep0141 "<span class='ref'>Data Forms Layout</span> <note>XEP-0141: Data Forms Layout &lt;<link url='http://www.xmpp.org/extensions/xep-0141.html'>http://www.xmpp.org/extensions/xep-0141.html</link>&gt;.</note>" >
<!ENTITY xep0142 "<span class='ref'>Workgroup Queues</span> <note>XEP-0142: Workgroup Queues &lt;<link url='http://www.xmpp.org/extensions/xep-0142.html'>http://www.xmpp.org/extensions/xep-0142.html</link>&gt;.</note>" >

View File

@ -38,7 +38,7 @@
<xs:element name='number' type='xs:byte'/>
<xs:element ref='status'/>
<xs:element ref='type'/>
<xs:element name='jig' type='xs:string'/>
<xs:element name='sig' type='xs:string'/>
<xs:element name='approver' type='xs:string'/>
<xs:element ref='dependencies'/>
<xs:element ref='supersedes'/>

51
xep.xsl
View File

@ -23,7 +23,7 @@
</meta>
<meta>
<xsl:attribute name='name'><xsl:text>DC.Publisher</xsl:text></xsl:attribute>
<xsl:attribute name='content'>Jabber Software Foundation</xsl:attribute>
<xsl:attribute name='content'>XMPP Standards Foundation</xsl:attribute>
</meta>
<meta>
<xsl:attribute name='name'><xsl:text>DC.Contributor</xsl:text></xsl:attribute>
@ -65,49 +65,49 @@
<xsl:variable name='thestatus' select='/xep/header/status'/>
<xsl:variable name='thetype' select='/xep/header/type'/>
<xsl:if test='$thestatus = "Active" and $thetype = "Historical"'>
<p style='color:green'>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.</p>
<p style='color:green'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Active" and $thetype = "Humorous"'>
<p style='color:green'>NOTICE: This document is Humorous. It MAY provide amusement but SHOULD NOT be taken seriously.</p>
</xsl:if>
<xsl:if test='$thestatus = "Active" and $thetype = "Informational"'>
<p style='color:green'>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.</p>
<p style='color:green'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Active" and $thetype = "Procedural"'>
<p style='color:green'>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.</p>
<p style='color:green'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Deferred"'>
<p style='color:red'>WARNING: Consideration of this document has been Deferred by the Jabber Software Foundation. Implementation of the protocol described herein is not recommended.</p>
<p style='color:red'>WARNING: Consideration of this document has been Deferred by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended.</p>
</xsl:if>
<xsl:if test='$thestatus = "Deprecated"'>
<p style='color:red'>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).</p>
<p style='color:red'>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).</p>
</xsl:if>
<xsl:if test='$thestatus = "Draft"'>
<p style='color:green'>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.</p>
<p style='color:green'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Experimental" and $thetype = "Historical"'>
<p style='color:red'>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.</p>
<p style='color:red'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Experimental" and $thetype = "Informational"'>
<p style='color:red'>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.</p>
<p style='color:red'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Experimental" and $thetype = "Procedural"'>
<p style='color:red'>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.</p>
<p style='color:red'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Experimental" and $thetype = "Standards Track"'>
<p style='color:red'>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.</p>
<p style='color:red'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Final"'>
<p style='color:green'>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.</p>
<p style='color:green'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "Obsolete"'>
<p style='color:red'>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).</p>
<p style='color:red'>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).</p>
</xsl:if>
<xsl:if test='$thestatus = "Proposed"'>
<p style='color:red'>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.</p>
<p style='color:red'>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.</p>
</xsl:if>
<xsl:if test='$thestatus = "ProtoXEP"'>
<p style='color:red'>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 &lt;<a href="http://www.xmpp.org/extensions/">http://www.xmpp.org/extensions/</a>&gt; and announced on the &lt;standards-jig@jabber.org&gt; mailing list.</p>
<p style='color:red'>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 &lt;<a href="http://www.xmpp.org/extensions/">http://www.xmpp.org/extensions/</a>&gt; and announced on the &lt;standards-jig@jabber.org&gt; mailing list.</p>
</xsl:if>
<xsl:if test='$thestatus = "Rejected"'>
<p style='color:red'>WARNING: This document has been Rejected by the XMPP Council. Implementation of the protocol described herein is not recommended under any circumstances.</p>
@ -119,6 +119,9 @@
<!-- XEP INFO -->
<h2>Document Information</h2>
<p class='indent'>
Series: <a href='http://www.xmpp.org/extensions/'>XEP</a><br />
Number: <xsl:value-of select='/xep/header/number'/><br />
Publisher: <a href='http://www.xmpp.org/xsf/'>XMPP Standards Foundation</a><br />
Status:
<a>
<xsl:attribute name='href'><xsl:text>http://www.xmpp.org/extensions/xep-0001.html#states-</xsl:text><xsl:value-of select='/xep/header/status'/></xsl:attribute>
@ -131,21 +134,19 @@
<xsl:value-of select='/xep/header/type'/>
</a>
<br />
Number: <xsl:value-of select='/xep/header/number'/><br />
Version: <xsl:value-of select='/xep/header/revision[position()=1]/version'/><br />
Last Updated: <xsl:value-of select='/xep/header/revision[position()=1]/date'/><br />
<xsl:variable name='expires.count' select='count(/xep/header/expires)'/>
<xsl:if test='$expires.count &gt; 0'>
Expires: <xsl:value-of select='/xep/header/expires'/><br />
</xsl:if>
Publishing Organization: <a href='http://www.jabber.org/jsf/'>Jabber Software Foundation</a><br />
<xsl:variable name='ApprovingBody' select='/xep/header/approver'/>
<xsl:choose>
<xsl:when test='$ApprovingBody = "Board"'>
Approving Body: <a href='http://www.jabber.org/board/'>JSF Board of Directors</a><br />
Approving Body: <a href='http://www.xmpp.org/board/'>XSF Board of Directors</a><br />
</xsl:when>
<xsl:otherwise>
Approving Body: <a href='http://www.jabber.org/council/'>XMPP Council</a><br />
Approving Body: <a href='http://www.xmpp.org/council/'>XMPP Council</a><br />
</xsl:otherwise>
</xsl:choose>
<xsl:variable name='dependencies.count' select='count(/xep/header/dependencies/spec)'/>
@ -196,7 +197,7 @@
<xsl:if test='$reg.count &gt; 0'>
Registry:
<xsl:variable name='registryURL'>
<xsl:text>http://www.jabber.org/registrar/</xsl:text>
<xsl:text>http://www.xmpp.org/registrar/</xsl:text>
<xsl:value-of select='/xep/header/shortname'/>
<xsl:text>.html</xsl:text>
</xsl:variable>
@ -226,13 +227,13 @@
<xsl:variable name='Approver' select='/xep/header/approver'/>
<xsl:choose>
<xsl:when test='$Approver = "Board"'>
<p class='indent'>The preferred venue for discussion of this document is the Standards-JIG discussion list: &lt;<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>&gt;.</p>
<p class='indent'>Discussion by the membership of the JSF may also be appropriate (see &lt;<a href="http://mail.jabber.org/mailman/listinfo/members">http://mail.jabber.org/mailman/listinfo/members</a>&gt; for details).</p>
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: &lt;<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>&gt;.</p>
<p class='indent'>Discussion by the membership of the XSF may also be appropriate (see &lt;<a href="http://mail.jabber.org/mailman/listinfo/members">http://mail.jabber.org/mailman/listinfo/members</a>&gt; for details).</p>
</xsl:when>
<xsl:otherwise>
<p class='indent'>The preferred venue for discussion of this document is the Standards-JIG discussion list: &lt;<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>&gt;.</p>
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: &lt;<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>&gt;.</p>
<xsl:if test='contains(/xep/header/dependencies,"RFC")'>
<p class='indent'>Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the JSF-IETF list may also be appropriate (see &lt;<a href="http://mail.jabber.org/mailman/listinfo/jsf-ietf">http://mail.jabber.org/mailman/listinfo/jsf-ietf</a>&gt; for details).</p>
<p class='indent'>Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the XSF-IETF list may also be appropriate (see &lt;<a href="http://mail.jabber.org/mailman/listinfo/jsf-ietf">http://mail.jabber.org/mailman/listinfo/jsf-ietf</a>&gt; for details).</p>
</xsl:if>
</xsl:otherwise>
</xsl:choose>
@ -240,7 +241,7 @@
<!-- (we don't put these on Procedural XEPs) -->
<xsl:if test='$thetype = "Standards Track" or $thetype = "Historical" or $thetype = "Informational"'>
<h2>Relation to XMPP</h2>
<p class='indent'>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.</p>
<p class='indent'>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.</p>
<h2>Conformance Terms</h2>
<p class='indent'>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".</p>
</xsl:if>