moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

xhtml fixes

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@537 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-02-14 03:13:44 +00:00
parent 24c54ffcba
commit 41cffc7579
6 changed files with 65 additions and 65 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
all.shtml
View File

@ -1,12 +1,13 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>XMPP Extensions</title> <title>XMPP Extensions</title>
<!--#include virtual="/includes/head.txt" --> <!--#include virtual='/includes/head.txt' -->
<h2>XMPP Extensions</h2> <h2>XMPP Extensions</h2>
<p><a class="standardsButton" href="atom.xml">ATOM</a>&nbsp;&nbsp;<a class="standardsButton" href="rss.xml">RSS</a></p> <p><a class='standardsButton' href='atom.xml'>ATOM</a>&nbsp;&nbsp;<a class='standardsButton' href='rss.xml'>RSS</a></p>
<p>This page lists all <a href="/extensions/">XMPP Extension Protocols</a> published by the XMPP Standards Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.</p> <p>This page lists all <a href='/extensions/'>XMPP Extension Protocols</a> published by the XMPP Standards Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.</p>
<p><em>Note: The following table is sortable, just click on the headers (click twice to reverse the sort order).</em></p> <p><em>Note: The following table is sortable, just click on the headers (click twice to reverse the sort order).</em></p>
@ -19,9 +20,9 @@
<th align='left'>Date</th> <th align='left'>Date</th>
</tr> </tr>
<!--#include virtual="/includes/xeps-all.txt" --> <!--#include virtual='/includes/xeps-all.txt' -->
</table> </table>
</div> </div>
<!--#include virtual="/includes/foot.txt" --> <!--#include virtual='/includes/foot.txt' -->

17
editor.shtml
View File

@ -1,21 +1,22 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>XMPP Extensions Editor</title> <title>XMPP Extensions Editor</title>
<!--#include virtual="/includes/head.txt" --> <!--#include virtual='/includes/head.txt' -->
<h2>XMPP Extensions Editor</h2> <h2>XMPP Extensions Editor</h2>
<p>In accordance with <a href="xep-0001.html">XEP-0001</a>, the XMPP Extensions Editor is responsible for overall management of the XMPP Standards Foundation's standards process and publication of <a href="/extensions/">XMPP Extension Protocols</a>; in particular, the XMPP Extensions Editor:</p> <p>In accordance with <a href='xep-0001.html'>XEP-0001</a>, the XMPP Extensions Editor is responsible for overall management of the XMPP Standards Foundation's standards process and publication of <a href='/extensions/'>XMPP Extension Protocols</a>; in particular, the XMPP Extensions Editor:</p>
<ul> <ul>
<li>works with XEP authors</li> <li>works with XEP authors</li>
<li>ensures that each XEP is properly formatted</li> <li>ensures that each XEP is properly formatted</li>
<li>assigns a unique number to each XEP</li> <li>assigns a unique number to each XEP</li>
<li>assigns or modifies the status of each XEP</li> <li>assigns or modifies the status of each XEP</li>
<li>maintains each XEP under <a href="http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/jeps/">source control</a></li> <li>maintains each XEP under <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/jeps/'>source control</a></li>
<li>maintains the canonical <a href="/extensions/">list of XEPs</a></li> <li>maintains the canonical <a href='/extensions/'>list of XEPs</a></li>
<li>publishes each XEP to the xmpp.org website</li> <li>publishes each XEP to the xmpp.org website</li>
<li>publicly announces the existence and status of each XEP</li> <li>publicly announces the existence and status of each XEP</li>
<li>gathers and tallies the votes of the <a href="/council/">XMPP Council</a></li> <li>gathers and tallies the votes of the <a href='/council/'>XMPP Council</a></li>
<li>fulfills the responsibilities of the <a href="/registrar/">XMPP Registrar</a></li> <li>fulfills the responsibilities of the <a href='/registrar/'>XMPP Registrar</a></li>
</ul> </ul>
<p>Since the founding of the <a href='/xsf/'>XMPP Standards Foundation</a> in 2001, the XMPP Extensions Editor has been <a href="/xsf/people/stpeter.shtml">Peter Saint-Andre</a>, who may be contacted via email or Jabber at &lt;&#101;&#100;&#105;&#116;&#111;&#114;&#64;&#106;&#97;&#98;&#98;&#101;&#114;&#46;&#111;&#114;&#103&gt;.</p> <p>Since the founding of the <a href='/xsf/'>XMPP Standards Foundation</a> in 2001, the XMPP Extensions Editor has been <a href='/xsf/people/stpeter.shtml'>Peter Saint-Andre</a>, who may be contacted via email or Jabber at &lt;&#101;&#100;&#105;&#116;&#111;&#114;&#64;&#106;&#97;&#98;&#98;&#101;&#114;&#46;&#111;&#114;&#103&gt;.</p>
</div> </div>
<!--#include virtual="/includes/foot.txt" --> <!--#include virtual='/includes/foot.txt' -->

3
gps_datum.html
View File

@ -1,10 +1,11 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>GPS Datum Example</title> <title>GPS Datum Example</title>
</head> </head>
<body> <body>
<h1>GPS Datum Example</h1> <h1>GPS Datum Example</h1>
<p>The following example of GPS datum differences was kindly provided by Randy Steele of Apollo, Pennsylvania (URL: &lt;<a href="http://www.nb.net/~resteele/">http://www.nb.net/~resteele/</a>&gt;) and is archived here so that a permanent link is available from <a href="http://www.xmpp.org/extensions/sep-0080.html">XEP-0080: User Geolocation</a>.</p> <p>The following example of GPS datum differences was kindly provided to the <a href='http://www.xmpp.org/'>XMPP Standards Foundation</a> by Randy Steele of Apollo, Pennsylvania (URL: &lt;<a href='http://www.nb.net/~resteele/'>http://www.nb.net/~resteele/</a>&gt;) and is archived here so that a permanent link is available from <a href='http://www.xmpp.org/extensions/xep-0080.html'>XEP-0080: User Geolocation</a>.</p>
<p>BEGIN EXAMPLE</p> <p>BEGIN EXAMPLE</p>
<hr /> <hr />
<p>This is an example of the differences in the datums you can use with a GPS. <p>This is an example of the differences in the datums you can use with a GPS.

1
index.shtml
View File

@ -1,3 +1,4 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>XMPP Extensions</title> <title>XMPP Extensions</title>

85
ipr-policy.shtml
View File

@ -1,72 +1,67 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>XSF IPR Policy</title> <title>XSF IPR Policy</title>
<!--#include virtual="/includes/head.txt" --> <!--#include virtual='/includes/head.txt' -->
<h2>XSF IPR Policy</h2> <h2>XSF IPR Policy</h2>
<p>This document defines the official policy of the <a href='/xsf/'>XMPP Standards Foundation</a> regarding intellectual property rights (IPR) pertaining to <a href='/extensions/'>XMPP Extension Protocol</a> (XEPs) specifications.</p> <p>This document defines the official policy of the <a href='/xsf/'>XMPP Standards Foundation</a> regarding intellectual property rights (IPR) pertaining to <a href='/extensions/'>XMPP Extension Protocol</a> (XEPs) specifications.</p>
<p><em>Version 1.3</em></p> <p style='font-style: italic'>Version 1.3</p>
<p><hr></p> <hr />
<strong>Table of Contents:</strong><br><dl> <p style='font-weight: bold'>Table of Contents:</p>
<dt>1. <a href="#intro">Introduction</a></dt> <p>
<dl> 1. <a href='#intro'>Introduction</a>
<dt>1.1. <a href="#intro-history">History</a></dt> <br />&#160;&#160;&#160;1.1. <a href='#intro-history'>History</a>
<dt>1.2. <a href="#intro-role">Purpose</a></dt> <br />&#160;&#160;&#160;1.2. <a href='#intro-role'>Purpose</a>
</dl> <br />2. <a href='#terms'>Terms</a>
<dt>2. <a href="#terms">Terms</a></dt> <br />&#160;&#160;&#160;2.1. <a href='#xmpp'>XMPP</a>
<dl> <br />&#160;&#160;&#160;2.2. <a href='#extension'>XMPP Extension Protocol</a>
<dt>2.1. <a href="#xmpp">XMPP</a></dt> <br />&#160;&#160;&#160;2.3. <a href='#implementation'>Implementation</a>
<dt>2.2. <a href="#extension">XMPP Extension Protocol</a></dt> <br />&#160;&#160;&#160;2.4. <a href='#claim'>Intellectual Property Claim</a>
<dt>2.3. <a href="#implementation">Implementation</a></dt> <br />3. <a href='#contributing'>Terms of Contributing to XMPP Extensions</a>
<dt>2.4. <a href="#claim">Intellectual Property Claim</a></dt> <br />&#160;&#160;&#160;3.1. <a href='#contrib-ownership'>Ownership</a>
</dl> <br />&#160;&#160;&#160;3.2. <a href='#contrib-approval'>Approval of XMPP Extensions</a>
<dt>3. <a href="#contributing">Terms of Contributing to XMPP Extensions</a></dt> <br />&#160;&#160;&#160;3.3. <a href='#contrib-private'>A Note about Private Extensions</a>
<dl> <br />4. <a href='#legal'>Legal Notice</a>
<dt>3.1. <a href="#contrib-ownership">Ownership</a></dt> </p>
<dt>3.2. <a href="#contrib-approval">Approval of XMPP Extensions</a></dt> <hr />
<dt>3.3. <a href="#contrib-private">A Note about Private Extensions</a></dt> <h2>1. <a name='intro'></a>Introduction</h2>
</dl> <p>This document defines the official policy of the XMPP Standards Foundation (XSF) regarding intellectual property rights (IPR) as they pertain to extensions to XMPP in the form of XMPP Extension Protocol specifications (XEPs). [<a href='#note1'>1</a>]</p>
<dt>4. <a href="#legal">Legal Notice</a>
</dt>
</dl>
<p><hr></p>
<h2>1. <a name="intro"></a>Introduction</h2>
<p>This document defines the official policy of the XMPP Standards Foundation (XSF) regarding intellectual property rights (IPR) as they pertain to extensions to XMPP in the form of XMPP Extension Protocol specifications (XEPs). [<a href="#note1">1</a>]</p>
<blockquote> <blockquote>
<h3>1.1 <a name="intro-history"></a>History</h3> <h3>1.1 <a name='intro-history'></a>History</h3>
<p>The Jabber/XMPP protocols have been under development since 1998 and have been discussed and documented in public forums since January 1999 in the open-source projects that were a precursor to the XSF. Through force of history and activity since its founding in the summmer of 2001, the XSF has assumed responsibility for managing the evolution of the Jabber/XMPP protocols in two ways: (1) through working with the IETF to standardize the core protocols under the name Extensible Messaging and Presence Protocol (XMPP); and (2) through the definition of extensions to the core protocol in the XSF's XMPP Extension Protocol (XEP) specification series. Through this work, the XSF has in effect "homesteaded" the domain of XMPP Extensions and has acted as a trusted third party or "intellectual property conservancy" [<a href="#note2">2</a>] to which new and established participants in the Jabber community have entrusted their XMPP Extensions.</p> <p>The Jabber/XMPP protocols have been under development since 1998 and have been discussed and documented in public forums since January 1999 in the open-source projects that were a precursor to the XSF. Through force of history and activity since its founding in the summmer of 2001, the XSF has assumed responsibility for managing the evolution of the Jabber/XMPP protocols in two ways: (1) through working with the IETF to standardize the core protocols under the name Extensible Messaging and Presence Protocol (XMPP); and (2) through the definition of extensions to the core protocol in the XSF's XMPP Extension Protocol (XEP) specification series. Through this work, the XSF has in effect "homesteaded" the domain of XMPP Extensions and has acted as a trusted third party or "intellectual property conservancy" [<a href='#note2'>2</a>] to which new and established participants in the Jabber community have entrusted their XMPP Extensions.</p>
<h3>1.2 <a name="intro-role"></a>Purpose</h3> <h3>1.2 <a name='intro-role'></a>Purpose</h3>
<p>The XSF does not seek to disparage the legitimate rights of any individual or organization to assert ownership over an Implementation of XMPP or of any XMPP Extension. However, the XSF must ensure that XMPP Extensions do not pollute the free and open nature of the protocols. Preventing such pollution means that in perpetuity any entity may independently, and without payment or hindrance, create, use, sell, distribute, or dispose of implementations of XMPP and of any XMPP Extension. Such is the intent of this policy.</p> <p>The XSF does not seek to disparage the legitimate rights of any individual or organization to assert ownership over an Implementation of XMPP or of any XMPP Extension. However, the XSF must ensure that XMPP Extensions do not pollute the free and open nature of the protocols. Preventing such pollution means that in perpetuity any entity may independently, and without payment or hindrance, create, use, sell, distribute, or dispose of implementations of XMPP and of any XMPP Extension. Such is the intent of this policy.</p>
</blockquote> </blockquote>
<h2>2. <a name="terms"></a>Terms</h2> <h2>2. <a name='terms'></a>Terms</h2>
<blockquote> <blockquote>
<h3>2.1 <a name="xmpp"></a>XMPP</a> <h3>2.1 <a name='xmpp'></a>XMPP</a>
</h3> </h3>
<p>The core XML streaming, instant messaging, and presence protocols developed by the Jabber community have been contributed by the XSF to the Internet Engineering Task Force (IETF) under the name Extensible Messaging and Presence Protocol (XMPP). XMPP is all and only these core protocols, as currently defined in <a href='http://www.ietf.org/rfc/rfc3920.txt'>RFC 3920</a> and <a href='http://www.ietf.org/rfc/rfc3921.txt'>RFC 3921</a>.</p> <p>The core XML streaming, instant messaging, and presence protocols developed by the Jabber community have been contributed by the XSF to the Internet Engineering Task Force (IETF) under the name Extensible Messaging and Presence Protocol (XMPP). XMPP is all and only these core protocols, as currently defined in <a href='http://www.ietf.org/rfc/rfc3920.txt'>RFC 3920</a> and <a href='http://www.ietf.org/rfc/rfc3921.txt'>RFC 3921</a>.</p>
</blockquote> </blockquote>
<blockquote> <blockquote>
<h3>2.2 <a name="extension"></a>XMPP Extension</h3> <h3>2.2 <a name='extension'></a>XMPP Extension</h3>
<p>For the purposes of this IPR policy, an XMPP Extension is any specification approved by, or submitted for approval or consideration by, the XSF or its constituent committees (most particularly the <a href='/council/'>XMPP Council</a>). Such a specification must exist in the form of a standards-track XMPP Extension Protocol (XEP) specification in order to be considered an official submission. (Also referred to as an Extension.)</p> <p>For the purposes of this IPR policy, an XMPP Extension is any specification approved by, or submitted for approval or consideration by, the XSF or its constituent committees (most particularly the <a href='/council/'>XMPP Council</a>). Such a specification must exist in the form of a standards-track XMPP Extension Protocol (XEP) specification in order to be considered an official submission. (Also referred to as an Extension.)</p>
</blockquote> </blockquote>
<blockquote> <blockquote>
<h3>2.3 <a name="implementation"></a>Implementation</h3> <h3>2.3 <a name='implementation'></a>Implementation</h3>
<p>Any software that implements XMPP or XMPP Extensions for the purpose of providing the functionality defined by the relevant specification(s).</p> <p>Any software that implements XMPP or XMPP Extensions for the purpose of providing the functionality defined by the relevant specification(s).</p>
</blockquote> </blockquote>
<blockquote> <blockquote>
<h3>2.4 <a name="claim"></a>Intellectual Property Claim</h3> <h3>2.4 <a name='claim'></a>Intellectual Property Claim</h3>
<p>Any patent, copyright, or other proprietary claim or claims made by an entity regarding a XMPP Extension. (Also referred to as a Claim.)</p> <p>Any patent, copyright, or other proprietary claim or claims made by an entity regarding a XMPP Extension. (Also referred to as a Claim.)</p>
</blockquote> </blockquote>
<h2>3. <a name="contributing"></a>Terms of Contributing an XMPP Extension</h2> <h2>3. <a name='contributing'></a>Terms of Contributing an XMPP Extension</h2>
<p>The XSF recognizes the possibility that the creator of an XMPP Extension may make an Intellectual Property Claim regarding an XMPP Extension. Therefore, the XSF takes the following positions:</p> <p>The XSF recognizes the possibility that the creator of an XMPP Extension may make an Intellectual Property Claim regarding an XMPP Extension. Therefore, the XSF takes the following positions:</p>
<blockquote> <blockquote>
<h3>3.1 <a name="contrib-ownership"></a>Ownership</h3> <h3>3.1 <a name='contrib-ownership'></a>Ownership</h3>
<p>By submitting an XMPP Extension for consideration by the XSF, the author of the Extension shall assign any ownership rights or other Claims asserted over the Extension to the XSF. This does not apply to Claims regarding any Implementations of the Extension, but rather to the Extension itself. Any documentation of the Extension (in the form of a XEP specification) shall be copyrighted by the XSF. Once an author assigns ownership to the XSF, the XSF shall in turn make the Extension available to all entities so that they may create, use, sell, distribute, or dispose of implementations of XMPP and all XMPP Extensions in perpetuity and without payment or hindrance.</p> <p>By submitting an XMPP Extension for consideration by the XSF, the author of the Extension shall assign any ownership rights or other Claims asserted over the Extension to the XSF. This does not apply to Claims regarding any Implementations of the Extension, but rather to the Extension itself. Any documentation of the Extension (in the form of a XEP specification) shall be copyrighted by the XSF. Once an author assigns ownership to the XSF, the XSF shall in turn make the Extension available to all entities so that they may create, use, sell, distribute, or dispose of implementations of XMPP and all XMPP Extensions in perpetuity and without payment or hindrance.</p>
</p> </p>
<h3>3.3 <a name="contrib-approval"></a>Approval of Extensions</h3> <h3>3.3 <a name='contrib-approval'></a>Approval of Extensions</h3>
<p>No Extension shall be approved by the XSF or its constituent committees if there are Claims to the Extension itself, or any Claims that would prevent perpetual, unrestricted, royalty-free use of the Extension in a compliant Implementation by any interested party. If Claims preventing such use are discovered, the XSF shall immediately seek to replace the Extension with unencumbered protocols that may be implemented without condition by any entity.</p> <p>No Extension shall be approved by the XSF or its constituent committees if there are Claims to the Extension itself, or any Claims that would prevent perpetual, unrestricted, royalty-free use of the Extension in a compliant Implementation by any interested party. If Claims preventing such use are discovered, the XSF shall immediately seek to replace the Extension with unencumbered protocols that may be implemented without condition by any entity.</p>
<h3>3.3 <a name="contrib-private"></a>A Note about Private Extensions</h3> <h3>3.3 <a name='contrib-private'></a>A Note about Private Extensions</h3>
<p>By its nature as XML, XMPP enables implementers to create their own private extensions to XMPP within custom XML namespaces. Such extensions may be kept private, and there is no compulsion for implementers to contribute such extensions to the Jabber community. It is only when an implementer seeks to have an extension standardized through the XSF's public standards process that ownership over such an extension must be transferred to the XSF. If an implementer wishes to keep its extensions private, it may simply refrain from submitting them to the XSF. However, private extensions exist outside the boundaries of XMPP and approved XMPP Extensions and must not be considered or described as part of XMPP or XSF-approved XMPP Extensions.</p> <p>By its nature as XML, XMPP enables implementers to create their own private extensions to XMPP within custom XML namespaces. Such extensions may be kept private, and there is no compulsion for implementers to contribute such extensions to the Jabber community. It is only when an implementer seeks to have an extension standardized through the XSF's public standards process that ownership over such an extension must be transferred to the XSF. If an implementer wishes to keep its extensions private, it may simply refrain from submitting them to the XSF. However, private extensions exist outside the boundaries of XMPP and approved XMPP Extensions and must not be considered or described as part of XMPP or XSF-approved XMPP Extensions.</p>
</blockquote> </blockquote>
<h2>5. <a name="legal"></a>Legal Notice</h2> <h2>5. <a name='legal'></a>Legal Notice</h2>
<p>All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notice:</p> <p>All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notice:</p>
<blockquote><pre> <blockquote><pre>
This XMPP Extension Protocol is copyright 1999 - [year] This XMPP Extension Protocol is copyright 1999 - [year]
@ -77,10 +72,10 @@ This material may be distributed only subject to the terms and
conditions set forth in the Creative Commons Attribution conditions set forth in the Creative Commons Attribution
License (&lt;http://creativecommons.org/licenses/by/2.5/&gt;). License (&lt;http://creativecommons.org/licenses/by/2.5/&gt;).
</pre></blockquote> </pre></blockquote>
<p><hr></p> <hr />
<h3>Notes</h3> <h3>Notes</h3>
<p><a name="note1"></a>1. For information about XMPP Extension Protocols, see &lt;<a href="http://www.xmpp.org/extensions/">http://www.xmpp.org/extensions/</a>&gt; and <a href="http://www.xmpp.org/extensions/xep-0001.html">XEP-0001</a>.</p> <p><a name='note1'></a>1. For information about XMPP Extension Protocols, see &lt;<a href='http://www.xmpp.org/extensions/'>http://www.xmpp.org/extensions/</a>&gt; and <a href='http://www.xmpp.org/extensions/xep-0001.html'>XEP-0001</a>.</p>
<p><a name="note2"></a>2. For information about intellectual property conservancies, see &lt;<a href="http://www.creativecommons.org/concepts/#ip">http://www.creativecommons.org/concepts/#ip</a>&gt; and M. van Houweling, "Cultivating Open Information Platforms: A Land Trust Model." <cite>Journal of Telecommunications &amp; High Technology Law</cite> 1, no. 1 (2002): 309-23.</p> <p><a name='note2'></a>2. For information about intellectual property conservancies, see &lt;<a href='http://www.creativecommons.org/concepts/#ip'>http://www.creativecommons.org/concepts/#ip</a>&gt; and M. van Houweling, "Cultivating Open Information Platforms: A Land Trust Model." <cite>Journal of Telecommunications &amp; High Technology Law</cite> 1, no. 1 (2002): 309-23.</p>
<h3>Acknowledgements</h3> <h3>Acknowledgements</h3>
<p>Many thanks to Lawrence Lessig and Molly van Houweling for their assistance in formulating this policy.</p> <p>Many thanks to Lawrence Lessig and Molly van Houweling for their assistance in formulating this policy.</p>
<h3>Changelog</h3> <h3>Changelog</h3>
@ -89,4 +84,4 @@ License (&lt;http://creativecommons.org/licenses/by/2.5/&gt;).
<p>Version 1.1 (2005-10-04): Replaced Open Publication License with Creative Commons Attribution License.</p> <p>Version 1.1 (2005-10-04): Replaced Open Publication License with Creative Commons Attribution License.</p>
<p>Version 1.0 (2002-10-29): Initial version approved by XSF Board of Directors.</p> <p>Version 1.0 (2002-10-29): Initial version approved by XSF Board of Directors.</p>
</div> </div>
<!--#include virtual="/includes/foot.txt" --> <!--#include virtual='/includes/foot.txt' -->

13
submit.shtml
View File

@ -1,15 +1,16 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
<html> <html>
<head> <head>
<title>How to Submit an XMPP Extension Protocol</title> <title>How to Submit an XMPP Extension Protocol</title>
<!--#include virtual="/includes/head.txt" --> <!--#include virtual='/includes/head.txt' -->
<h2>How to Submit an XMPP Extension Protocol</h2> <h2>How to Submit an XMPP Extension Protocol</h2>
<p>Here is how to submit a proposal to the XMPP Standards Foundation for consideration as an XMPP Extension Protocol:</p> <p>Here is how to submit a proposal to the XMPP Standards Foundation for consideration as an XMPP Extension Protocol:</p>
<ol> <ol>
<li><p>Contact the <a href="editor.shtml">XMPP Extensions Editor</a> so that he knows to expect your submission.</p></li> <li><p>Contact the <a href='editor.shtml'>XMPP Extensions Editor</a> so that he knows to expect your submission.</p></li>
<li><p>Write your proposal following the guidelines described in <a href="/extensions/xep-0143.html">XEP-0143: Guidelines for Authors of XMPP Extension Protocols</a>.</p></li> <li><p>Write your proposal following the guidelines described in <a href='/extensions/xep-0143.html'>XEP-0143: Guidelines for Authors of XMPP Extension Protocols</a>.</p></li>
<li>Make sure you read, understand, and agree to the XSF's <a href="/extensions/ipr-policy.shtml">IPR Policy</a> before you submit your proposal!</li> <li>Make sure you read, understand, and agree to the XSF's <a href='/extensions/ipr-policy.shtml'>IPR Policy</a> before you submit your proposal!</li>
<li><p>Email the XML file (or a URL for the file) to the <a href="editor.shtml">XMPP Extensions Editor</a> with a subject line of "ProtoXEP: [your title here]".</li> <li><p>Email the XML file (or a URL for the file) to the <a href='editor.shtml'>XMPP Extensions Editor</a> with a subject line of 'ProtoXEP: [your title here]'.</li>
</ol> </ol>
<p><strong>Note:</strong> It is the author's responsibility to provide a properly-formatted source file (see the <a href='template.xml'>template</a> and <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/'>CVS repository</a>). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.</p> <p><strong>Note:</strong> It is the author's responsibility to provide a properly-formatted source file (see the <a href='template.xml'>template</a> and <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/'>CVS repository</a>). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.</p>
</div> </div>
<!--#include virtual="/includes/foot.txt" --> <!--#include virtual='/includes/foot.txt' -->