mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-21 15:18:51 -05:00
WordPress URLs
This commit is contained in:
stpeter
parent
d583974016
commit
69a7304ce0
@ -222,7 +222,7 @@
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Submission Process' anchor='submission'>
|
||||
<p>The XSF welcomes and encourages the submission of protocols to the XSF's standards process. <note>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.</note> 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. <a name='states-ProtoXEP'></a> 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 <<link url="http://www.xmpp.org/extensions/submit.shtml">http://www.xmpp.org/extensions/submit.shtml</link>>). All submissions to the XSF's standards process should be directed to the XMPP Extensions Editor.</p>
|
||||
<p>The XSF welcomes and encourages the submission of protocols to the XSF's standards process. <note>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.</note> 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. <a name='states-ProtoXEP'></a> 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 <<link url="http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/">http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/</link>>). All submissions to the XSF's standards process should be directed to the XMPP Extensions Editor.</p>
|
||||
<p>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!</p>
|
||||
<p>All proposals submitted to the XSF for consideration as XEPs must contain the following information:</p>
|
||||
<ol start='1'>
|
||||
@ -245,7 +245,7 @@
|
||||
<li>assign it a number</li>
|
||||
<li>specify an appropriate type</li>
|
||||
<li>specify a status of Experimental</li>
|
||||
<li>add it to source control <note>XEPs are kept under source control in the 'xmpp' module and 'extensions' directory of the XSF Subversion repository; instructions for accessing these files can be found at <<link url='http://www.xmpp.org/xsf/sourcecontrol.shtml'>http://www.xmpp.org/xsf/sourcecontrol.shtml</link>>.</note></li>
|
||||
<li>add it to source control <note>XEPs are kept under source control in the 'xmpp' module and 'extensions' directory of the XSF Subversion repository; instructions for accessing these files can be found at <<link url='http://xmpp.org/about-xmpp/xsf/xsf-source-control/'>http://xmpp.org/about-xmpp/xsf/xsf-source-control/</link>>.</note></li>
|
||||
<li>add tracking information to the XEPs database</li>
|
||||
<li>publish version 0.1 of the XEP to the xmpp.org website <note>The canonical URL for accessing XMPP Extensions is <<link url='http://www.xmpp.org/extensions/'>http://www.xmpp.org/extensions/</link>>.</note></li>
|
||||
<li>publicly announce the existence of the XEP by sending a message to the Standards list</li>
|
||||
|
||||
10
xep.ent
10
xep.ent
@ -6,7 +6,7 @@
|
||||
|
||||
This file is maintained by the XMPP Extensions Editor:
|
||||
|
||||
http://xmpp.org/extensions/editor.shtml
|
||||
http://xmpp.org/about-xmpp/xsf/xsf-people/#editor
|
||||
|
||||
Please do not add entities to this file; instead,
|
||||
add them to the relevant XEP and then ask the Editor
|
||||
@ -225,7 +225,7 @@ THE SOFTWARE.
|
||||
<permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions>
|
||||
<warranty>## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##</warranty>
|
||||
<liability>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.</liability>
|
||||
<conformance>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <<link url='http://xmpp.org/extensions/ipr-policy.shtml'>http://xmpp.org/extensions/ipr-policy.shtml</link>> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).</conformance>
|
||||
<conformance>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <<link url='http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/'>http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/</link>> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).</conformance>
|
||||
</legal>" >
|
||||
|
||||
<!-- other XSF-related text shortcuts -->
|
||||
@ -241,13 +241,13 @@ THE SOFTWARE.
|
||||
<!-- common XSF-related URLs -->
|
||||
|
||||
<!ENTITY BOARD "<span class='ref'><link url='http://xmpp.org/xsf/board/'>XSF Board of Directors</link></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 <<link url='http://xmpp.org/xsf/board/'>http://xmpp.org/xsf/board/</link>>.</note>" >
|
||||
<!ENTITY BYLAWS "<span class='ref'><link url='http://xmpp.org/xsf/docs/bylaws.shtml'>XSF Bylaws</link></span> <note>The Bylaws of the XMPP Standards Foundation (XSF) define the legal basis and operating procedures of the XSF. For further information, see <<link url='http://xmpp.org/xsf/docs/bylaws.shtml'>http://xmpp.org/xsf/docs/bylaws.shtml</link>>.</note>" >
|
||||
<!ENTITY BYLAWS "<span class='ref'><link url='http://xmpp.org/about-xmpp/xsf/xsf-bylaws/'>XSF Bylaws</link></span> <note>The Bylaws of the XMPP Standards Foundation (XSF) define the legal basis and operating procedures of the XSF. For further information, see <<link url='http://xmpp.org/about-xmpp/xsf/xsf-bylaws/'>http://xmpp.org/about-xmpp/xsf/xsf-bylaws/</link>>.</note>" >
|
||||
<!ENTITY COUNCIL "<span class='ref'><link url='http://xmpp.org/council/'>XMPP Council</link></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 <<link url='http://xmpp.org/council/'>http://xmpp.org/council/</link>>.</note>" >
|
||||
<!ENTITY EDITOR "<span class='ref'><link url='http://xmpp.org/extensions/editor.shtml'>XMPP Extensions Editor</link></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 <<link url='http://xmpp.org/extensions/editor.shtml'>http://xmpp.org/extensions/editor.shtml</link>>.</note>" >
|
||||
<!ENTITY EDITOR "<span class='ref'><link url='http://xmpp.org/about-xmpp/xsf/xsf-people/#editor'>XMPP Extensions Editor</link></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 <<link url='http://xmpp.org/about-xmpp/xsf/xsf-people/#editor'>http://xmpp.org/about-xmpp/xsf/xsf-people/#editor</link>>.</note>" >
|
||||
<!ENTITY XMPPICA "<span class='ref'><link url='http://xmpp.org/ca/'>XMPP Intermediate Certification Authority</link></span> <note>The XMPP Intermediate Certification Authority (ICA) issues free domain certificates to administrators of XMPP-based services. For further information, see <<link url='http://xmpp.org/ca/'>http://xmpp.org/ca/</link>>.</note>" >
|
||||
<!ENTITY XSF "<span class='ref'><link url='http://xmpp.org/xsf/'>XMPP Standards Foundation (XSF)</link></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 <<link url='http://xmpp.org/xsf/'>http://xmpp.org/xsf/</link>>.</note>" >
|
||||
<!ENTITY XSFIETF "<span class='ref'><link url='http://mail.jabber.org/mailman/listinfo/jsf-ietf/'>XSF-IETF list</link></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 <<link url='http://mail.jabber.org/mailman/listinfo/jsf-ietf/'>http://mail.jabber.org/mailman/listinfo/jsf-ietf/</link>>.</note>" >
|
||||
<!ENTITY XSFIPR "<span class='ref'><link url='http://xmpp.org/extensions/ipr-policy.shtml'>XSF IPR Policy</link></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 <<link url='http://xmpp.org/extensions/ipr-policy.shtml'>http://xmpp.org/extensions/ipr-policy.shtml</link>>.</note>" >
|
||||
<!ENTITY XSFIPR "<span class='ref'><link url='http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/'>XSF IPR Policy</link></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 <<link url='http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/'>http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/</link>>.</note>" >
|
||||
<!ENTITY REGISTRAR "<span class='ref'><link url='http://xmpp.org/registrar/'>XMPP Registrar</link></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 <<link url='http://xmpp.org/registrar/'>http://xmpp.org/registrar/</link>>.</note>" >
|
||||
<!ENTITY SSIG "<span class='ref'><link url='http://mail.jabber.org/mailman/listinfo/standards/'>Standards SIG</link></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 <<link url='http://mail.jabber.org/mailman/listinfo/standards/'>http://mail.jabber.org/mailman/listinfo/standards/</link>>.</note>" >
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user