link correction

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

xep-0080.xml

@@ -314,7 +314,7 @@
   <p>Avoid "Mars probe" issues: as specified in Table 1, the units for &lt;lat/&gt; and &lt;lon/&gt; MUST be decimal degrees (where South and West are negative, North and East are positive), the units for &lt;alt/&gt; MUST be meters above or below sea level, and the units for &lt;error/&gt; MUST be arc minutes.</p>
   <p>In applications where updates are sent whenever there is a certain distance change in location, those applications SHOULD account for time as well, to avoid rate-limiting when the user is (for example) on a jet plane. One possible way to do this would be to send updates at most once per minute of time (every time 60 seconds have elapsed).</p>
   <p>Inferences SHOULD NOT be made about accuracy from the number of digits specified in the location or altitude.</p>
-  <p>Why the datum madness? See &lt;<link url='http://www.jabber.org/protocol/geoloc/gps_datum.html'>http://www.jabber.org/protocol/geoloc/gps_datum.html</link>&gt; for an example.</p>
+  <p>Why the datum madness? See &lt;<link url='http://www.xmpp.org/extensions/gps_datum.html'>http://www.xmpp.org/extensions/gps_datum.html</link>&gt; for an example.</p>
   <p>An entity can provide a GPS path by publishing a series of items (i.e., multiple pubsub events) with appropriate values of the &lt;timestamp/&gt; element.</p>
 </section1>