JEP to XEP

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@27 4b5297f7-1745-476d-ba37-a9c6900126ab
guusdk · Oct 3, 2006 · 86f6eb0 · 86f6eb0
1 parent ba3ae90
commit 86f6eb0
Show file tree

Hide file tree

Showing 29 changed files with 1,233 additions and 584 deletions.
diff --git a/xep-0001.xml b/xep-0001.xml
diff --git a/xep-0002.xml b/xep-0002.xml
@@ -1,10 +1,10 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE jep SYSTEM '../jep.dtd' [
-  <!ENTITY % ents SYSTEM '../jep.ent'>
+<!DOCTYPE xep SYSTEM 'xep.dtd' [
+  <!ENTITY % ents SYSTEM 'xep.ent'>
 %ents;
 ]>
-<?xml-stylesheet type='text/xsl' href='../jep.xsl'?>
-<jep>
+<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
+<xep>
 <header>
   <title>Jabber Interest Groups (JIGs)</title>
   <abstract>A definition of Jabber Interest Groups, including their structure and role within the Jabber Software Foundation.</abstract>
@@ -32,11 +32,11 @@
   </revision>
 </header>
 <section1 topic='Short Definition'>
-  <p>A Jabber Interest Group (JIG) is a working group approved by the Jabber Council to address specific areas of growth or concern within the Jabber community, usually by means of developing and publishing Jabber Enhancements Proposals (JEPs).</p>
+  <p>A Jabber Interest Group (JIG) is a working group approved by the XMPP Council to address specific areas of growth or concern within the Jabber/XMPP developer community, usually by means of developing and publishing XMPP Extension Protocols (XEPs).</p>
 </section1>
 <section1 topic='Explanation'>
-  <p>The main function of most JIGs is to produce acceptable enhancements to the Jabber protocol (delivered in the form of Jabber Enhancement Proposals or JEPs <note>For information about Jabber Enhancement Proposals, see <link url="http://foundation.jabber.org/jeps/jep-0001.html">http://foundation.jabber.org/jeps/jep-0001.html</link>.</note>) within a reasonably limited period of time. However, at the discretion of the Jabber Council, a handful of standing JIGs may be approved (e.g., to address security or standards compliance).</p>
-  <p>Anyone (not limited to members of the Jabber Software Foundation) may propose the formation of a JIG by completing a Jabber Enhancement Proposal outlining the need for the JIG and its proposed focus. However, JIG leaders must be members of the Jabber Software Foundation. The number of leaders for a JIG is flexible, and shall be determined by each JIG, in consultation with the Jabber Council if necessary. The concept of "membership" with regard to JIGs is loose, and is essentially co-extensive with membership in the appropriate mailing list (each JIG has its own mailing list, which is archived for public review). JIG members do not need to be members of the Jabber Software Foundation, and any member of the general public may subscribe to JIG mailing lists.</p>
-  <p>It is expected that all JIGs (other than certain standing JIGs) will remain active for as long as necessary in order to produce one or more standards-track JEPs for review by the Jabber Council in the JIG's area of focus. However, if a JIG does not show signs of activity for an extended period of time (usually six months of inactivity on the JIG's mailing list), the JIG may be disbanded at the discretion of the Jabber Council with appropriate warning to the JIG members (usually in the form of an email sent to the JIG's mailing list).</p>
+  <p>The main function of most JIGs is to produce acceptable XMPP extensions (delivered in the form of XMPP Extension Protocols or XEPs <note>For information about XMPP Extension Protocols, see <link url="http://www.xmpp.org/extensions/xep-0001.html">http://www.xmpp.org/extensions/xep-0001.html</link>.</note>) within a reasonably limited period of time. However, at the discretion of the XMPP Council, a handful of standing JIGs may be approved (e.g., to address security or standards compliance).</p>
+  <p>Anyone (not limited to members of the Jabber Software Foundation) may propose the formation of a JIG by completing a XMPP Extension Protocol outlining the need for the JIG and its proposed focus. However, JIG leaders must be members of the Jabber Software Foundation. The number of leaders for a JIG is flexible, and shall be determined by each JIG, in consultation with the XMPP Council if necessary. The concept of "membership" with regard to JIGs is loose, and is essentially co-extensive with membership in the appropriate mailing list (each JIG has its own mailing list, which is archived for public review). JIG members do not need to be members of the Jabber Software Foundation, and any member of the general public may subscribe to JIG mailing lists.</p>
+  <p>It is expected that all JIGs (other than certain standing JIGs) will remain active for as long as necessary in order to produce one or more standards-track JEPs for review by the XMPP Council in the JIG's area of focus. However, if a JIG does not show signs of activity for an extended period of time (usually six months of inactivity on the JIG's mailing list), the JIG may be disbanded at the discretion of the XMPP Council with appropriate warning to the JIG members (usually in the form of an email sent to the JIG's mailing list).</p>
 </section1>
-</jep>
+</xep>
diff --git a/xep-0003.xml b/xep-0003.xml
@@ -1,13 +1,13 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE jep SYSTEM '../jep.dtd' [
-  <!ENTITY % ents SYSTEM '../jep.ent'>
+<!DOCTYPE xep SYSTEM 'xep.dtd' [
+  <!ENTITY % ents SYSTEM 'xep.ent'>
 %ents;
 ]>
-<?xml-stylesheet type='text/xsl' href='../jep.xsl'?>
-<jep>
+<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
+<xep>
 <header>
   <title>Proxy Accept Socket Service (PASS)</title>
-  <abstract>A proposal for proxy support in Jabber.</abstract>
+  <abstract>This document defines a method for relaying media via proxies on the Jabber/XMPP network.</abstract>
   &LEGALNOTICE;
   <number>0003</number>
   <status>Active</status>
@@ -20,7 +20,7 @@
   <supersededby/>
   <shortname>pass</shortname>
   <schemaloc>
-    <url>http://jabber.org/protocol/pass/pass.xsd</url>
+    <url>http://www.xmpp.org/schemas/pass.xsd</url>
   </schemaloc>
   &jer;
   &reatmon;
@@ -292,10 +292,10 @@
   </section2>
 </section1>
 <section1 topic='IANA Considerations'>
-  <p>This JEP requires no interaction with &IANA;.</p>
+  <p>This document requires no interaction with &IANA;.</p>
 </section1>
-<section1 topic='Jabber Registrar Considerations'>
-  <p>No action on the part of the &REGISTRAR; is necessary as a result of this JEP, since 'jabber:iq:pass' is already a registered protocol namespace.</p>
+<section1 topic='XMPP Registrar Considerations'>
+  <p>No action on the part of the &REGISTRAR; is necessary as a result of this document, since 'jabber:iq:pass' is already a registered protocol namespace.</p>
 </section1>
 <section1 topic='XML Schema'>
   <code><![CDATA[
@@ -310,7 +310,7 @@
   <xs:annotation>
     <xs:documentation>
       The protocol documented by this schema is defined in
-      JEP-0003: http://www.jabber.org/jeps/jep-0003.html
+      XEP-0003: http://www.xmpp.org/extensions/xep-0003.html
     </xs:documentation>
   </xs:annotation>
 
@@ -344,4 +344,4 @@
 </xs:schema>
     ]]></code>
 </section1>
-</jep>
+</xep>