1.4pre1

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1589 4b5297f7-1745-476d-ba37-a9c6900126ab
2025-02-07 02:40:22 -05:00 · 2008-01-18 03:51:46 +00:00 · 2008-01-18 03:51:46 +00:00 · ec978187aa
commit ec978187aa
parent 1a331f6c24
1 changed files with 20 additions and 17 deletions
--- a/ipr-policy.shtml
+++ b/ipr-policy.shtml
@ -4,8 +4,8 @@
 <title>XSF IPR Policy</title>
 <!--#include virtual='/includes/head.txt' -->
 <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> specifications (XEPs).</p>
-<p style='font-style: italic'>Version 1.3</p>
+<p style='font-style: italic'>Version 1.4</p>
 <hr />
 <p style='font-weight: bold'>Table of Contents:</p>
 <p>
@ -28,18 +28,18 @@
 <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>
  <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/XMPP developer community have entrusted their XMPP Extensions.</p>
  <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 or Deployment 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>
 <h2>2.  <a name='terms'></a>Terminology</h2>
 <blockquote>
  <h3>2.1 <a name='xmpp'></a>XMPP</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/XMPP developer 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>
  <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>
  <h3>2.3 <a name='implementation'></a>Implementation</h3>
-  <p>Any software program that implements the functionality defined in the core XMPP specifications or in XMPP Extensions Protocols for the purpose of providing the functionality defined by the relevant specification(s).</p>
+  <p>Any software program that implements the functionality defined in the core XMPP specifications or in XMPP Extension Protocols for the purpose of providing the functionality defined by the relevant specification(s).</p>
  <h3>2.4 <a name='deployment'></a>Deployment</h3>
  <p>Any service deployed over a network that offers the capabilities defined in the core XMPP specifications or in XMPP Extension Protocols.</p>
  <h3>2.5 <a name='claim'></a>Intellectual Property Claim</h3>
@ -53,26 +53,29 @@
  <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 or Deployment 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>
-  <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 by means of custom XML namespaces. Such extensions may be kept private, and there is no compulsion for implementers to contribute such extensions to the Jabber/XMPP developer 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>
 <h2>4.  <a name='legal'></a>Legal Notices</h2>
 <p>All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notices:</p>
-<blockquote><pre>
+<blockquote>
-This XMPP Extension Protocol is copyright 1999 - [year] 
+<h3>Copyright</h3>This XMPP Extension Protocol is copyright (c) 1999 - 2008 by the XMPP Standards Foundation (XSF).
-by the XMPP Standards Foundation (XSF) and is in full
+<h3>Permissions</h3>
-conformance with the XSF's Intellectual Property Rights 
+<p>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.</p>
-Policy (&lt;http://www.xmpp.org/extensions/ipr-policy.shtml&gt;). 
+<h3>Disclaimer of Warranty</h3>
-This material may be distributed only subject to the terms and
+<p><span style="font-weight: bold">## 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. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</span></p>
-conditions set forth in the Creative Commons Attribution
+<h3>Limitation of Liability</h3>
-License (&lt;http://creativecommons.org/licenses/by/2.5/&gt;).
+<p>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 out of the use or inability to use 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.</p>
-</pre></blockquote>
+<h3>IPR Conformance</h3>
-<hr />
+<p>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at &lt;<a href="http://www.xmpp.org/extensions/ipr-policy.shtml">http://www.xmpp.org/extensions/ipr-policy.shtml</a>&gt; or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).</p>
 </blockquote>
 <hr/>
 <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='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; as well as 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>
 <p>Many thanks to Lawrence Lessig and Molly van Houweling for their assistance in formulating this policy.</p>
 <h3>Changelog</h3>
 <p>Version 1.4 (2008-01-17): Modified legal notices to use modified MIT License rather than Creative Commons Attribution License for the purpose of enabling wider distribution of XEP text and examples, including incorporation into free software; added Disclaimer of Warrant and Limitation of Liability.</p>
 <p>Version 1.3 (2007-01-16): Modified terminology to reflect organizational name change from Jabber Software Foundation (JSF) to XMPP Standards Foundation (XSF).</p>
 <p>Version 1.2 (2006-10-04): Modified terminology to reflect protocol branding change from Jabber to XMPP (e.g., Jabber Enhancement Proposal to XMPP Extension Protocol).</p>
 <p>Version 1.1 (2005-10-04): Replaced Open Publication License with Creative Commons Attribution License.</p>