From 0aab53ba92c4cd92624c2c71e348859dd5a85b37 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Mon, 14 Nov 2016 11:46:11 -0600 Subject: [PATCH] XEP-0001: Fix minor DTD and whitespace issues --- xep-0001.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xep-0001.xml b/xep-0001.xml index 43863bba..52310331 100644 --- a/xep-0001.xml +++ b/xep-0001.xml @@ -11,8 +11,8 @@ &LEGALNOTICE; 0001 Active - Procedural + Procedural None Board @@ -241,7 +241,7 @@ -

The XSF welcomes and encourages the submission of protocols to the XSF's standards process. It is important to understand that private extensions to XMPP are also allowed. The XSF does not, and cannot, require such private extensions to be added to the public, official set of protocols recognized by the XSF. The processes and procedures in this document apply only to protocols that are submitted to the XSF, not to private protocol extensions used for custom functionality in particular applications. However, such private extensions must not be considered part of the protocols recognized by the XSF. Any individual or group of individuals may author a proposal and submit it to the XSF for consideration as a XEP, and there is no requirement that a XEP author shall be an elected member of the XSF. Proposals to define official XSF protocols must be presented in the XEP format and must follow the rules defined herein (after a proposal has been submitted but before it has been accepted as a XEP, it is known informally as a "ProtoXEP"). The authoring and submission process is defined in &xep0143; (see also <http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/>). All submissions to the XSF's standards process should be directed to the XMPP Extensions Editor.

+

The XSF welcomes and encourages the submission of protocols to the XSF's standards process. It is important to understand that private extensions to XMPP are also allowed. The XSF does not, and cannot, require such private extensions to be added to the public, official set of protocols recognized by the XSF. The processes and procedures in this document apply only to protocols that are submitted to the XSF, not to private protocol extensions used for custom functionality in particular applications. However, such private extensions must not be considered part of the protocols recognized by the XSF. Any individual or group of individuals may author a proposal and submit it to the XSF for consideration as a XEP, and there is no requirement that a XEP author shall be an elected member of the XSF. Proposals to define official XSF protocols must be presented in the XEP format and must follow the rules defined herein (after a proposal has been submitted but before it has been accepted as a XEP, it is known informally as a "ProtoXEP"). The authoring and submission process is defined in &xep0143; (see also <http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/>). All submissions to the XSF's standards process should be directed to the XMPP Extensions Editor.

Note well that XEP authors must transfer ownership of their protocols (but not implementations thereof) to the XSF. Refer to the &XSFIPR; for details. XEP authors must make sure that they have read, understood, and agreed to the XSF IPR Policy before submitting a proposal to the XMPP Extensions Editor!

All proposals submitted to the XSF for consideration as XEPs must contain the following information:

    @@ -451,9 +451,9 @@ THE SOFTWARE. Protocols (XEPs). For further information about XEPs, visit: http://www.xmpp.org/extensions/ - + The canonical URL for this schema is: - + http://www.xmpp.org/extensions/xep.xsd