diff --git a/all.shtml b/all.shtml index 201e6a5d..30755dbf 100755 --- a/all.shtml +++ b/all.shtml @@ -24,5 +24,4 @@ - diff --git a/editor.shtml b/editor.shtml index 1a662e74..5e23316f 100755 --- a/editor.shtml +++ b/editor.shtml @@ -17,6 +17,6 @@
  • gathers and tallies the votes of the XMPP Council
  • fulfills the responsibilities of the XMPP Registrar
    • -

    Since the founding of the XMPP Standards Foundation in 2001, the XMPP Extensions Editor has been Peter Saint-Andre, who may be contacted via email or Jabber at <editor@jabber.org>.

    +

    Since the founding of the XMPP Standards Foundation in 2001, the XMPP Extensions Editor has been Peter Saint-Andre, who may be contacted via email or Jabber at <editor@jabber.org>.

    diff --git a/gps_datum.html b/gps_datum.html index fb19ef98..c1f4b0d6 100644 --- a/gps_datum.html +++ b/gps_datum.html @@ -8,17 +8,8 @@

    The following example of GPS datum differences was kindly provided to the XMPP Standards Foundation by Randy Steele of Apollo, Pennsylvania (URL: <http://www.nb.net/~resteele/>) and is archived here so that a permanent link is available from XEP-0080: User Geolocation.

    BEGIN EXAMPLE

    -

    This is an example of the differences in the datums you can use with a GPS. -Below is a site I was checking out. I marked it on my GPS in the field. When I got back -home to find it on the topo map, I noticed something was not right. Using -the UTM coordinates from the GPS, I located the site on the topo map. But -the map site and the site I checked in the field did not match. The terrain -was different, the site I actually checked was near the road (the top red -circle). I then remembered about map datums. The topo map was made to NAD27, while -my GPS was set to WGS84. After changing the GPS to the NAD27 datum, all was fine. -So the moral of this story is: MAKE SURE THE GPS DATUM AND THE MAP DATUM MATCH!!! -Note the difference in the circle locations. I also changed my GPS datum to NAD27.

    -

    GPS Datum Example +

    This is an example of the differences in the datums you can use with a GPS. Below is a site I was checking out. I marked it on my GPS in the field. When I got back home to find it on the topo map, I noticed something was not right. Using the UTM coordinates from the GPS, I located the site on the topo map. But the map site and the site I checked in the field did not match. The terrain was different, the site I actually checked was near the road (the top red circle). I then remembered about map datums. The topo map was made to NAD27, while my GPS was set to WGS84. After changing the GPS to the NAD27 datum, all was fine. So the moral of this story is: MAKE SURE THE GPS DATUM AND THE MAP DATUM MATCH!!! Note the difference in the circle locations. I also changed my GPS datum to NAD27.

    +

    GPS Datum Example

    END EXAMPLE

    diff --git a/ipr-policy.shtml b/ipr-policy.shtml index 8c950ed0..13fc111c 100755 --- a/ipr-policy.shtml +++ b/ipr-policy.shtml @@ -25,45 +25,37 @@

    1. Introduction

    -

    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). [1]

    -
    -

    1.1 History

    +

    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). [1]

    +
    +

    1.1 History

    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" [2] to which new and established participants in the Jabber community have entrusted their XMPP Extensions.

    -

    1.2 Purpose

    +

    1.2 Purpose

    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.

    -
    +

    2. Terms

    -
    -

    2.1 XMPP -

    -

    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 RFC 3920 and RFC 3921.

    -
    -
    -

    2.2 XMPP Extension

    -

    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 XMPP Council). 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.)

    -
    -
    -

    2.3 Implementation

    -

    Any software that implements XMPP or XMPP Extensions for the purpose of providing the functionality defined by the relevant specification(s).

    -
    -
    +
    +

    2.1 XMPP

    +

    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 RFC 3920 and RFC 3921.

    +

    2.2 XMPP Extension

    +

    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 XMPP Council). 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.)

    +

    2.3 Implementation

    +

    Any software that implements XMPP or XMPP Extensions for the purpose of providing the functionality defined by the relevant specification(s).

    2.4 Intellectual Property Claim

    Any patent, copyright, or other proprietary claim or claims made by an entity regarding a XMPP Extension. (Also referred to as a Claim.)

    3. Terms of Contributing an XMPP Extension

    -

    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:

    -
    -

    3.1 Ownership

    -

    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.

    -

    -

    3.3 Approval of Extensions

    -

    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.

    -

    3.3 A Note about Private Extensions

    -

    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.

    -
    -

    5. Legal Notice

    -

    All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notice:

    - 
    +
    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:
    
+
    
+  
    3.1 Ownership
    
+  
    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.
    
+  
    3.3 Approval of Extensions
    
+  
    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.
    
+  
    3.3 A Note about Private Extensions
    
+  
    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.
    
+
    
+
    4.  Legal Notice
    
+
    All XMPP Extension Protocol (XEP) specifications shall contain the following Legal Notice:
    
+
     This XMPP Extension Protocol is copyright 1999 - [year] 
 by the XMPP Standards Foundation (XSF) and is in full
 conformance with the XSF's Intellectual Property Rights 
@@ -71,7 +63,7 @@ Policy (<http://www.xmpp.org/extensions/ipr-policy.shtml>).
 This material may be distributed only subject to the terms and
 conditions set forth in the Creative Commons Attribution
 License (<http://creativecommons.org/licenses/by/2.5/>).
-  
    
+

    Notes

    1. For information about XMPP Extension Protocols, see <http://www.xmpp.org/extensions/> and XEP-0001.

    @@ -83,5 +75,4 @@ License (<http://creativecommons.org/licenses/by/2.5/>).

    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).

    Version 1.1 (2005-10-04): Replaced Open Publication License with Creative Commons Attribution License.

    Version 1.0 (2002-10-29): Initial version approved by XSF Board of Directors.

    - diff --git a/submit.shtml b/submit.shtml index e3288382..90530bee 100755 --- a/submit.shtml +++ b/submit.shtml @@ -8,9 +8,8 @@

    1. Contact the XMPP Extensions Editor so that he knows to expect your submission.

    2. Write your proposal following the guidelines described in XEP-0143: Guidelines for Authors of XMPP Extension Protocols.

      3. -
    3. Make sure you read, understand, and agree to the XSF's IPR Policy before you submit your proposal!
      4. -

    4. Email the XML file (or a URL for the file) to the XMPP Extensions Editor with a subject line of 'ProtoXEP: [your title here]'.

      5. +
    5. Make sure you read, understand, and agree to the XSF's IPR Policy before you submit your proposal!

      6. +

    6. Email the XML file (or a URL for the file) to the XMPP Extensions Editor with a subject line of 'ProtoXEP: [your title here]'.

    Note: It is the author's responsibility to provide a properly-formatted source file (see the template and CVS repository). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.

    -