mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-24 10:12:19 -05:00
xmpp.org addresses
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@353 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
dd87357c71
commit
8590e2c4be
@ -95,8 +95,8 @@ elif (xepstatus == "Deferred"):
|
||||
|
||||
## SEND MAIL:
|
||||
#
|
||||
# From: editor@jabber.org
|
||||
# To: standards-jig@jabber.org
|
||||
# From: editor@xmpp.org
|
||||
# To: standards@xmpp.org
|
||||
# Subject: UPDATED: XEP-$xepnum ($title)
|
||||
# [or "NEW..." if version 0.1]
|
||||
# Body:
|
||||
@ -106,11 +106,11 @@ elif (xepstatus == "Deferred"):
|
||||
# CVS Diff: $mods
|
||||
# URL: http://www.xmpp.org/extensions/xep-$xepnum.html
|
||||
|
||||
fromaddr = "editor@jabber.org"
|
||||
fromaddr = "editor@xmpp.org"
|
||||
# for testing...
|
||||
# toaddrs = "stpeter@jabber.org"
|
||||
# for real...
|
||||
toaddrs = "standards-jig@jabber.org"
|
||||
toaddrs = "standards@xmpp.org"
|
||||
|
||||
if xepflag == "new":
|
||||
thesubject = 'NEW: XEP-'
|
||||
|
||||
@ -70,8 +70,8 @@ remark = getText(remarkNode.childNodes)
|
||||
|
||||
# SEND MAIL:
|
||||
#
|
||||
# From: editor@jabber.org
|
||||
# To: standards-jig@jabber.org
|
||||
# From: editor@xmpp.org
|
||||
# To: standards@xmpp.org
|
||||
# Subject: DEFERRED: XEP-$xepnum ($title)
|
||||
# Body:
|
||||
# XEP-$xepnum ($title) has been Deferred because of inactivity.
|
||||
@ -84,11 +84,11 @@ remark = getText(remarkNode.childNodes)
|
||||
# its status will be changed back to Experimental.
|
||||
#
|
||||
|
||||
fromaddr = "editor@jabber.org"
|
||||
fromaddr = "editor@xmpp.org"
|
||||
# for testing...
|
||||
# toaddrs = "stpeter@jabber.org"
|
||||
# for real...
|
||||
toaddrs = "standards-jig@jabber.org"
|
||||
toaddrs = "standards@xmpp.org"
|
||||
|
||||
thesubject = 'DEFERRED: XEP-' + xepnum + " (" + title + ")"
|
||||
introline = 'XEP-' + xepnum + ' (' + title + ') has been Deferred because of inactivity.'
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
|
||||
<p><a class="standardsButton" href="atom.xml">ATOM</a> <a class="standardsButton" href="rss.xml">RSS</a></p>
|
||||
|
||||
<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards-jig/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">"inbox"</a>). Changes are tracked via a <a href="http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/">CVS repository</a> (see <a href='http://www.jabberstudio.org/cvs.php'>instructions</a>), <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
|
||||
<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">"inbox"</a>). Changes are tracked via a <a href="http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/">CVS repository</a> (see <a href='http://www.jabberstudio.org/cvs.php'>instructions</a>), <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
|
||||
|
||||
<p>This page lists approved XMPP extensions as well as proposals that are under active consideration. A <a href="all.shtml">list of all XEPs</a> (including retracted, rejected, deprecated, and obsolete XEPs) is also available. Good places for developers to start are the <a href='xep-0073.html'>basic</a> and <a href='xep-0117.html'>intermediate</a> protocol suites.</p>
|
||||
|
||||
|
||||
8
inxep.py
8
inxep.py
@ -68,8 +68,8 @@ remark = getText(remarkNode.childNodes)
|
||||
|
||||
# SEND MAIL:
|
||||
#
|
||||
# From: editor@jabber.org
|
||||
# To: standards-jig@jabber.org
|
||||
# From: editor@xmpp.org
|
||||
# To: standards@xmpp.org
|
||||
# Subject: Proposed XMPP Extension: XEP-$xepnum ($title)
|
||||
# Body:
|
||||
# The XMPP Extensions Editor has received a proposal for a new XEP.
|
||||
@ -84,11 +84,11 @@ remark = getText(remarkNode.childNodes)
|
||||
# this proposal as a full XEP.
|
||||
#
|
||||
|
||||
fromaddr = "editor@jabber.org"
|
||||
fromaddr = "editor@xmpp.org"
|
||||
# for testing...
|
||||
# toaddrs = "stpeter@jabber.org"
|
||||
# for real...
|
||||
toaddrs = "standards-jig@jabber.org"
|
||||
toaddrs = "standards@xmpp.org"
|
||||
|
||||
thesubject = 'Proposed XMPP Extension: ' + title
|
||||
introline = 'The XMPP Extensions Editor has received a proposal for a new XEP.'
|
||||
|
||||
@ -72,8 +72,8 @@ remark = getText(remarkNode.childNodes)
|
||||
|
||||
# SEND MAIL:
|
||||
#
|
||||
# From: editor@jabber.org
|
||||
# To: standards-jig@jabber.org
|
||||
# From: editor@xmpp.org
|
||||
# To: standards@xmpp.org
|
||||
# Subject: LAST CALL: XEP-$xepnum ($title)
|
||||
# Body:
|
||||
# This message constitutes notice of a Last Call
|
||||
@ -87,11 +87,11 @@ remark = getText(remarkNode.childNodes)
|
||||
# of business on $enddate.
|
||||
#
|
||||
|
||||
fromaddr = "editor@jabber.org"
|
||||
fromaddr = "editor@xmpp.org"
|
||||
# for testing...
|
||||
# toaddrs = "stpeter@jabber.org"
|
||||
# for real...
|
||||
toaddrs = "standards-jig@jabber.org"
|
||||
toaddrs = "standards@xmpp.org"
|
||||
|
||||
thesubject = 'LAST CALL: XEP-' + xepnum + " (" + title + ")"
|
||||
introline = 'This message constitutes notice of a Last Call for XEP-' + xepnum + ' (' + title + ').'
|
||||
|
||||
@ -83,7 +83,7 @@
|
||||
<section1 topic='Registry Creation and Maintenance' anchor='registries'>
|
||||
<p>Every XMPP Extension Protocol specification (XEP) must contain a section devoted to "XMPP Registrar Considerations", detailing the namespaces and parameters to be registered with the XMPP Registrar, as well as any new registries to be created as a result of the XEP.</p>
|
||||
<p>The registry additions or creations specified in an XMPP Extension Protocol specification shall not take effect until the document advances to a status of Draft (Standards-Track XEPs) or Active (Informational and Historical XEPs). Registration of namespaces shall be handled as described in the <link url='#namespaces'>Namespace Issuance</link> section of this document. Registration of particular parameters used within a specification shall be initiated by the XMPP Extensions Editor if specified in the XEP, and may also be initiated by implementors of the XMPP Extension Protocol document after it has advanced to Active, Draft, or Final. Creation of new registries shall be initiated by the XMPP Registrar; if a document specifies the creation of a new registry, the author is strongly encouraged to consult with the XMPP Registrar before seeking a Last Call on the XEP.</p>
|
||||
<p>Requests for parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to <<link url='mailto:registrar@jabber.org'>mailto:registrar@jabber.org</link>>. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SSIG;. The Registrar shall add registry items at its discretion based on discussion within the Standards SIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementor thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.</p>
|
||||
<p>Requests for parameter assignments must be sent to the XMPP Registrar in accordance with the process specified in the document (usually a XEP) that defines the relevant registry, normally by sending an appropriately formatted email message to <<link url='mailto:registrar@xmpp.org'>mailto:registrar@xmpp.org</link>>. If, in the Registrar's judgment, discussion of a request is required, the Registrar shall initiate such discussion within the &SSIG;. The Registrar shall add registry items at its discretion based on discussion within the Standards SIG if necessary, but shall not unduly restrict registration of parameter values. If a document author or implementor thinks that a request was unfairly denied by the Registrar, an appeal of the decision may be directed to the XMPP Council.</p>
|
||||
<p>The XMPP Registrar shall maintain registries of assigned namespaces and parameters at <<link url="http://www.xmpp.org/registrar/">http://www.xmpp.org/registrar/</link>> and shall update those registries in a timely fashion. Changes to the registries shall be announced on the Standards mailing list.</p>
|
||||
</section1>
|
||||
<section1 topic='Namespace Issuance' anchor='namespaces'>
|
||||
|
||||
@ -216,7 +216,7 @@ Additional information: This media type is not to be confused
|
||||
with the "application/xmpp+xml" media type, which is for
|
||||
use by native XMPP applications.
|
||||
Person and email address to contact for further information:
|
||||
XMPP Registrar, <registrar@jabber.org>
|
||||
XMPP Registrar, <registrar@xmpp.org>
|
||||
Intended usage: COMMON
|
||||
Author/Change controller: XSF, XMPP Registrar
|
||||
]]></code>
|
||||
|
||||
@ -473,7 +473,7 @@
|
||||
<name>PSA</name>
|
||||
</item>
|
||||
<item id='23456'>
|
||||
<uri scheme='mailto'>editor@jabber.org</uri>
|
||||
<uri scheme='mailto'>editor@xmpp.org</uri>
|
||||
<name>XMPP Extensions Editor</name>
|
||||
</item>
|
||||
</query>
|
||||
@ -499,7 +499,7 @@
|
||||
<name>PSA</name>
|
||||
</item>
|
||||
<item id='23456'>
|
||||
<uri scheme='mailto'>editor@jabber.org</uri>
|
||||
<uri scheme='mailto'>editor@xmpp.org</uri>
|
||||
<name>XMPP Extensions Editor</name>
|
||||
</item>
|
||||
</query>
|
||||
|
||||
@ -75,7 +75,7 @@
|
||||
<p>These functions are specified below.</p>
|
||||
|
||||
<section2 topic='Accepting a XEP' anchor='accepting'>
|
||||
<p>Periodically, people send mail to editor@jabber.org with new proposals. Here is how to process such submissions.</p>
|
||||
<p>Periodically, people send email to editor@xmpp.org with new proposals. Here is how to process such submissions.</p>
|
||||
<ol>
|
||||
<li>Receive proposal from author.</li>
|
||||
<li>Give it a descriptive filename that does <em>not</em> include the string 'xep' or a XEP number.</li>
|
||||
@ -224,19 +224,19 @@
|
||||
<ol>
|
||||
<li>
|
||||
<p>announce.py</p>
|
||||
<p>This script announces a new version of a XEP by updating the database and sending a message to standards-jig@jabber.org.</p>
|
||||
<p>This script announces a new version of a XEP by updating the database and sending a message to standards@xmpp.org.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>deferrred.py</p>
|
||||
<p>This script updates the database and sends a message to standards-jig@jabber.org when the status of a XEP is changed to Deferred. Before running this script, make sure that you modify the <status/> element in the XEP itself and run the gen.sh shell script.</p>
|
||||
<p>This script updates the database and sends a message to standards@xmpp.org when the status of a XEP is changed to Deferred. Before running this script, make sure that you modify the <status/> element in the XEP itself and run the gen.sh shell script.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>lastcall.py</p>
|
||||
<p>This script announces a Last Call for a XEP by updating the database and sending a message to standards-jig@jabber.org.</p>
|
||||
<p>This script announces a Last Call for a XEP by updating the database and sending a message to standards@xmpp.org.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>protoxep.py</p>
|
||||
<p>This script announces availability of a new "proto-XEP" (i.e., a document not yet accepted as a XEP by the XMPP Council) by sending a message to standards-jig@jabber.org. Before running this script, place the new proto-XEP so that it is available at http://www.xmpp.org/extensions/inbox/ (normally this is done by running 'xsltproc inbox/docname.xml > /var/www/xmpp.org/extensions/inbox/docname.html' from the editor's working CVS directory on the web server).</p>
|
||||
<p>This script announces availability of a new "proto-XEP" (i.e., a document not yet accepted as a XEP by the XMPP Council) by sending a message to standards@xmpp.org. Before running this script, place the new proto-XEP so that it is available at http://www.xmpp.org/extensions/inbox/ (normally this is done by running 'xsltproc inbox/docname.xml > /var/www/xmpp.org/extensions/inbox/docname.html' from the editor's working CVS directory on the web server).</p>
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
|
||||
4
xep.ent
4
xep.ent
@ -131,7 +131,7 @@
|
||||
|
||||
<!ENTITY BOOLEANNOTE "<note>In accordance with Section 3.2.2.1 of <cite>XML Schema Part 2: Datatypes</cite>, the allowable lexical representations for the xs:boolean datatype are the strings "0" and "false" for the concept 'false' and the strings "1" and "true" for the concept 'true'; implementations MUST support both styles of lexical representation.</note>" >
|
||||
|
||||
<!ENTITY REGPROCESS "<p>In order to submit new values to this registry, the registrant must define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address <registrar@jabber.org>:</p>" >
|
||||
<!ENTITY REGPROCESS "<p>In order to submit new values to this registry, the registrant must define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address <registrar@xmpp.org>:</p>" >
|
||||
|
||||
<!-- RFC 2119 reference -->
|
||||
|
||||
@ -147,7 +147,7 @@
|
||||
<!ENTITY XSFIETF "<span class='ref'>XSF-IETF list</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'>XSF IPR Policy</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://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>>.</note>" >
|
||||
<!ENTITY REGISTRAR "<span class='ref'>XMPP Registrar</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://www.xmpp.org/registrar/'>http://www.xmpp.org/registrar/</link>>.</note>" >
|
||||
<!ENTITY SSIG "<span class='ref'>Standards SIG</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-jig/'>http://mail.jabber.org/mailman/listinfo/standards-jig/</link>>.</note>" >
|
||||
<!ENTITY SSIG "<span class='ref'>Standards SIG</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>" >
|
||||
|
||||
<!-- various code projects -->
|
||||
|
||||
|
||||
6
xep.xsl
6
xep.xsl
@ -107,7 +107,7 @@
|
||||
<p style='color:red'>NOTICE: This document is currently within Last Call or under consideration by the XMPP Council for advancement to the next stage in the XSF standards process.</p>
|
||||
</xsl:if>
|
||||
<xsl:if test='$thestatus = "ProtoXEP"'>
|
||||
<p style='color:red'>WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document must not be referred to as an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <<a href="http://www.xmpp.org/extensions/">http://www.xmpp.org/extensions/</a>> and announced on the <standards-jig@jabber.org> mailing list.</p>
|
||||
<p style='color:red'>WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document must not be referred to as an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <<a href="http://www.xmpp.org/extensions/">http://www.xmpp.org/extensions/</a>> and announced on the <standards@xmpp.org> mailing list.</p>
|
||||
</xsl:if>
|
||||
<xsl:if test='$thestatus = "Rejected"'>
|
||||
<p style='color:red'>WARNING: This document has been Rejected by the XMPP Council. Implementation of the protocol described herein is not recommended under any circumstances.</p>
|
||||
@ -227,11 +227,11 @@
|
||||
<xsl:variable name='Approver' select='/xep/header/approver'/>
|
||||
<xsl:choose>
|
||||
<xsl:when test='$Approver = "Board"'>
|
||||
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: <<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>>.</p>
|
||||
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: <<a href="http://mail.jabber.org/mailman/listinfo/standards">http://mail.jabber.org/mailman/listinfo/standards</a>>.</p>
|
||||
<p class='indent'>Discussion by the membership of the XSF may also be appropriate (see <<a href="http://mail.jabber.org/mailman/listinfo/members">http://mail.jabber.org/mailman/listinfo/members</a>> for details).</p>
|
||||
</xsl:when>
|
||||
<xsl:otherwise>
|
||||
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: <<a href="http://mail.jabber.org/mailman/listinfo/standards-jig">http://mail.jabber.org/mailman/listinfo/standards-jig</a>>.</p>
|
||||
<p class='indent'>The preferred venue for discussion of this document is the Standards discussion list: <<a href="http://mail.jabber.org/mailman/listinfo/standards">http://mail.jabber.org/mailman/listinfo/standards</a>>.</p>
|
||||
<xsl:if test='contains(/xep/header/dependencies,"RFC")'>
|
||||
<p class='indent'>Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the XSF-IETF list may also be appropriate (see <<a href="http://mail.jabber.org/mailman/listinfo/jsf-ietf">http://mail.jabber.org/mailman/listinfo/jsf-ietf</a>> for details).</p>
|
||||
</xsl:if>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user