link fixes

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@349 4b5297f7-1745-476d-ba37-a9c6900126ab

all.shtml

@@ -6,7 +6,7 @@
 
 <p><a class="standardsButton" href="atom.xml">ATOM</a>&nbsp;&nbsp;<a class="standardsButton" href="rss.xml">RSS</a></p>
 
-<p>This page lists all <a href="/extensions/">XMPP Extension Protocols</a> published by the Jabber Software Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.</p>
+<p>This page lists all <a href="/extensions/">XMPP Extension Protocols</a> published by the XMPP Standards Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.</p>
  
 <p><em>Note: The following table is sortable, just click on the headers (click twice to reverse the sort order).</em></p>
 

archive.sh

@@ -2,6 +2,9 @@
 # archive an old version of a XEP (before publishing new version)
 # usage: ./archive.sh xepnum version 
 
+# STAGE
+#xeppath=/var/www/stage.xmpp.org/extensions
+# PRODUCTION
 xeppath=/var/www/xmpp.org/extensions
 
 cp $xeppath/xep-$1.html $xeppath/attic/xep-$1-$2.html

editor.shtml

@@ -3,7 +3,7 @@
 <title>XMPP Extensions Editor</title>
 <!--#include virtual="/includes/head.txt" -->
 <h2>XMPP Extensions Editor</h2>
-<p>In accordance with <a href="jep-0001.html">XEP-0001</a>, the XMPP Extensions Editor is responsible for overall management of the Jabber Software Foundation's standards process and publication of <a href="/extensions/">XMPP Extension Protocols</a>; in particular, the XMPP Extensions Editor:</p>
+<p>In accordance with <a href="xep-0001.html">XEP-0001</a>, the XMPP Extensions Editor is responsible for overall management of the XMPP Standards Foundation's standards process and publication of <a href="/extensions/">XMPP Extension Protocols</a>; in particular, the XMPP Extensions Editor:</p>
 <ul>
 <li>works with XEP authors</li>
 <li>ensures that each XEP is properly formatted</li>
@@ -16,6 +16,6 @@
 <li>gathers and tallies the votes of the <a href="/council/">XMPP Council</a></li>
 <li>fulfills the responsibilities of the <a href="/registrar/">XMPP Registrar</a></li>
 </ul>
-<p>Since the founding of the <a href='http://www.jabber.org/jsf/'>Jabber Software Foundation</a> in 2001, the XMPP Extensions Editor has been  <a href="http://www.jabber.org/people/stpeter.shtml">Peter Saint-Andre</a>, who may be contacted via &lt;&#101;&#100;&#105;&#116;&#111;&#114;&#64;&#106;&#97;&#98;&#98;&#101;&#114;&#46;&#111;&#114;&#103&gt;.</p>
+<p>Since the founding of the <a href='/xsf/'>XMPP Standards Foundation</a> in 2001, the XMPP Extensions Editor has been <a href="/xsf/people/stpeter.shtml">Peter Saint-Andre</a>, who may be contacted via email or Jabber at &lt;&#101;&#100;&#105;&#116;&#111;&#114;&#64;&#106;&#97;&#98;&#98;&#101;&#114;&#46;&#111;&#114;&#103&gt;.</p>
 </div>
 <!--#include virtual="/includes/foot.txt" -->

index.shtml

@@ -6,7 +6,7 @@
 
 <p><a class="standardsButton" href="atom.xml">ATOM</a>&nbsp;&nbsp;<a class="standardsButton" href="rss.xml">RSS</a></p>
 
-<p>The <a href='http://www.jabber.org/jsf/'>Jabber Software Foundation</a> (JSF) develops extensions to <a href="http://www.xmpp.org/">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-JIG 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/">&quot;inbox&quot;</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-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/">&quot;inbox&quot;</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>
 

submit.shtml

@@ -3,11 +3,11 @@
 <title>How to Submit an XMPP Extension Protocol</title>
 <!--#include virtual="/includes/head.txt" -->
 <h2>How to Submit an XMPP Extension Protocol</h2>
-<p>Here is how to submit a proposal to the Jabber Software Foundation for consideration as an XMPP Extension Protocol:</p>
+<p>Here is how to submit a proposal to the XMPP Standards Foundation for consideration as an XMPP Extension Protocol:</p>
 <ol>
 <li><p>Contact the <a href="editor.shtml">XMPP Extensions Editor</a> so that he knows to expect your submission.</p></li>
 <li><p>Write your proposal following the guidelines described in <a href="/extensions/xep-0143.html">XEP-0143: Guidelines for Authors of XMPP Extension Protocols</a>.</p></li>
-<li>Make sure you read, understand, and agree to the JSF's <a href="/extensions/ipr-policy.shtml">IPR Policy</a> before you submit your proposal!</li>
+<li>Make sure you read, understand, and agree to the XSF's <a href="/extensions/ipr-policy.shtml">IPR Policy</a> before you submit your proposal!</li>
 <li><p>Email the XML file (or a URL for the file) to the <a href="editor.shtml">XMPP Extensions Editor</a> with a subject line of "ProtoXEP: [your title here]".</li>
 </ol>
 <p><strong>Note:</strong> It is the author's responsibility to provide a properly-formatted source file (see the <a href='template.xml'>template</a> and <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/'>CVS repository</a>). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.</p>

xep.xsl

@@ -121,7 +121,7 @@
           <p class='indent'>
             Series: <a href='http://www.xmpp.org/extensions/'>XEP</a><br />
             Number: <xsl:value-of select='/xep/header/number'/><br />
-            Publisher: <a href='http://www.xmpp.org/xsf/'>XMPP Standards Foundation</a><br />
+            Publisher: <a href='/xsf/'>XMPP Standards Foundation</a><br />
             Status: 
             <a>
               <xsl:attribute name='href'><xsl:text>http://www.xmpp.org/extensions/xep-0001.html#states-</xsl:text><xsl:value-of select='/xep/header/status'/></xsl:attribute>