XEP-0345: Form of Membership Applications

Abstract: This specification outlines the form and mandatory content of membership applications.
Author:Dave Cridland
Copyright:© 1999 - 2014 XMPP Standards Foundation. SEE LEGAL NOTICES.
Last Updated:2014-03-19

NOTICE: This Procedural document proposes that the process or activity defined herein shall be followed by the XMPP Standards Foundation (XSF). However, this process or activity has not yet been approved by the XMPP Council and/or the XSF Board of Directors and is therefore not currently in force.

Table of Contents

1. Introduction
2. Who May Apply
3. Where Applications Are Submitted
4. Challenges and Final Arbiter
5. Mandatory Information
    5.1. All Applicants
    5.2. Corporate Applicants
    5.3. Natural Applicants
6. Security Considerations
7. IANA Considerations
8. XMPP Registrar Considerations

    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History

1. Introduction

Prior to this specification, membership applications have been relatively informal, and guidance has been similarly ad-hoc. This document provides the form of membership applications, which is part of the remit of the XSF Board.

The intent is to provide as few rules as possible, but ensure that the XSF has the essential information required to make a decision on the application.

2. Who May Apply

Although at the time this document was written, the XSF has only ever had "natural persons" - that is, ordinary people - apply for membership, the XSF Bylaws [1] explicitly allow for corporate membership. In order to ensure the form of an application can satisfy this, this document will assume such applications may occur in the future.

This document will distinguish requirements by using the term "Applicant" to mean either type, "Natural Applicant" for actual people, and "Corporate Applicant" for legal entities other than natural persons.

3. Where Applications Are Submitted

Applications are to be submitted as a new Wiki Page on the XSF Wiki, and linked from a single Wiki page which will be included in the announcement email sent by the XSF Secretary.

Applicants are solely responsible for their own applications, and the applications shall be their own. Members and prospective members should not edit anyone else's application. Exceptions to this latter shall be made only with permission of the Board, the XSF Secretary, or the Executive Director; and the Applicant concerned.

4. Challenges and Final Arbiter

In the case that a particular application is questionable for some reason - if it is thought to be missing mandatory information or failing to disclose affiliations - a member may raise a Challenge with the membership, by sending a message to the members list detailing the issues. A member request a member of the XSF Board of Directors [2] to raise the Challenge anonymously on their behalf; the member of the Board however is in no way compelled to do so.

The XSF Board is the final arbiter of such Challenges, and shall make a final decision on whether the application should be rejected; however the Board is expected to take into account any rough consensus of the members. Any rejection will include any remedies possible.

Notwithstanding the final nature of the XSF Board's decision, any application so rejected may be resubmitted by the Applicant, presumably after addressing the issues.

5. Mandatory Information

The purpose of the mandatory information is to allow the XSF Secretary sufficient information to adhere to the XSF Bylaws. As a secondary purpose, it also allows the XSF members to make an informed decision when voting to accept applications; it is important for Applicants to understand that this mandatory information is unlikely to be sufficient to convince the members, however.

5.1 All Applicants

Applicants must provide:

Contact Email
A valid email address, specific to the Applicant, suitable for members to contact and request further information.
Contact Jid
A valid jid, specific to the Applicant, suitable for members to contact and request further information.

5.2 Corporate Applicants

Corporate Applicants must provide:

Relevant Affiliations
Any further affiliations, as described within the final clause of the XSF Bylaws, Section 2.1. Note that Corporate Applicants will always be assumed to represent themselves, and may have no further affiliations.
Legal Name
A full name by which the Applicant is known and identified for legal purposes. This could be the registered name of a Corporate Applicant.
Relevant Trading Styles
Many jurisdictions have the notion of names under which a business typically operates. Names used by the Corporate Applicant for trading any XMPP related products or services must be included. There is no requirement herein to list all XMPP products or services.

5.3 Natural Applicants

Natural Applicants must provide:

Relevant Affiliations
Any affiliations, as described within the final clause of the XSF Bylaws, Section 2.1. Note that this is not limited to employment.
Legal Name
A full name by which the Applicant is known and identified for legal purposes. This could be the name on a Natural Applicant's passport.

6. Security Considerations

There are privacy implications inherent in the public disclosure of the information in an Application, particularly by a Natural Applicant.

These are an unavoidable consequence of the Application.

7. IANA Considerations

This document has no considerations for IANA.

8. XMPP Registrar Considerations

This document has no considerations for the XMPP Registrar.


Appendix A: Document Information

Series: XEP
Number: 0345
Publisher: XMPP Standards Foundation
Status: Experimental
Type: Procedural
Version: 0.1
Last Updated: 2014-03-19
Approving Body: XSF Board of Directors
Dependencies: None
Supersedes: None
Superseded By: None
Short Name: N/A
Source Control: HTML
This document in other formats: XML  PDF

Appendix B: Author Information

Dave Cridland

Email: dave@cridland.net

Appendix C: Legal Notices


This XMPP Extension Protocol is copyright © 1999 - 2014 by the XMPP Standards Foundation (XSF).


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.

Disclaimer of 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. ##

Limitation of 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.

IPR 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 <http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion by the membership of the XSF might also be appropriate (see <http://mail.jabber.org/mailman/listinfo/members> for details).

Errata can be sent to <editor@xmpp.org>.

Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

Appendix G: Notes

1. The Bylaws of the XMPP Standards Foundation (XSF) define the legal basis and operating procedures of the XSF. For further information, see <http://xmpp.org/about-xmpp/xsf/xsf-bylaws/>.

2. 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 <http://xmpp.org/xsf/board/>.

Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.1 (2014-03-19)

Initial published version approved by XSF Board of Directors.

(editor (mam))

Version 0.0.2 (2014-02-26)

Fixed typos, added entities and mandatory sections.


Version 0.0.1 (2013-12-13)

Initial Version