Remove xml extension from internal article links

From author guidelines: “use the target's document name (without the .xml extension) as the link address.”

Author: joewiz

src/main/xar-resources/data/backup/backup.xml

@@ -323,7 +323,7 @@
                 <programlisting xlink:href="listings/listing-6.txt"/>
                 <para>You can also subscribe to the notifications made available by the SanityReport
                     MBean to be informed of sanity check results. Please consult eXist-db's <link
-                    xlink:href="jmx.xml">JMX documentation</link> on how to configure this.</para>
+                    xlink:href="jmx">JMX documentation</link> on how to configure this.</para>
             </sect3>
 
         </sect2>

src/main/xar-resources/data/basic-installation/basic-installation.xml

@@ -131,7 +131,7 @@
             </listitem>
             <listitem>
                 <para>More advanced installation methods (like installing on a headless system) are
-                    described in the <link xlink:href="advanced-installation.xml#headless">Advanced
+                    described in the <link xlink:href="advanced-installation#headless">Advanced
                     Installation</link> article. If you wish to compile and run exist from source
                     please see the article on <link xlink:href="exist-building.xml">building
                     eXist</link></para>
@@ -252,7 +252,7 @@
 
         <note>
             <para>eXist-db can also be run as a background service. For more information see the
-                <link xlink:href="advanced-installation.xml#headless">Advanced Installation</link>
+                <link xlink:href="advanced-installation#headless">Advanced Installation</link>
                 article.</para>
         </note>
 
@@ -318,14 +318,14 @@
                 <literal>bin/</literal> sub-directory. On Linux or Mac, enter
                 <code>bin/startup.sh</code>, on Windows <code>bin\startup.bat</code>. More
                 information about these start-up scripts in the <link
-                xlink:href="advanced-installation.xml#headless">Advanced Installation</link>
+                xlink:href="advanced-installation#headless">Advanced Installation</link>
                 article.</para>
 
             <note>
                 <title>Having trouble?</title>
                 <para>If you're having trouble launching eXist-db, see our articles on <link
                     xlink:href="troubleshooting">Troubleshooting</link> and <link
-                    xlink:href="advanced-installation.xml#headless">Advanced
+                    xlink:href="advanced-installation#headless">Advanced
                     Installation</link>.</para>
             </note>
         </sect2>
@@ -351,7 +351,7 @@
             </mediaobject>
         </informalfigure>
         <para>Seeing it? Congratulations! (Not seeing it? See our article on <link
-            xlink:href="troubleshooting.xml">Troubleshooting</link>).</para>
+            xlink:href="troubleshooting">Troubleshooting</link>).</para>
 
         <para>All right, ready to dive in! Your local installation includes everything you need.
             Access is easy, through the applications on the <link xlink:href="{dashboard}/"

src/main/xar-resources/data/beginners-guide-to-xrx-v4/beginners-guide-to-xrx-v4.xml

@@ -4,7 +4,7 @@
 
     <info>
         <title>Creating CRUDS applications with XRX in eXist</title>
-        <date>1Q18</date>
+        <date>2Q19</date>
         <keywordset>
             <keyword>getting-started</keyword>
             <keyword>application-development</keyword>
@@ -235,7 +235,8 @@
                     interchange of applications, the EXPath Community has created a specification
                     for application metadata, called EXPath Packaging System. eXist supports and
                     extends this module. This tutorial will not cover this file's structure, but you
-                    can learn more about this by reading <link xlink:href="https://exist-db.org/exist/apps/doc/repo.xml"/>. </para>
+                    can learn more about this by reading about the <link xlink:href="repo">Package 
+                        Repository</link>. </para>
             </listitem>
         </orderedlist>
         <para>You are always free to change the names of the collection or the queries, but as
@@ -400,7 +401,7 @@
                 also creates a Lucene full text index for all words in the term name, term
                 definition and term publish-status-code. (By using the repo.xml Deployment
                 Descriptor's "prepare" field, you can automate the installation of this
-                collection.xconf file into the target location; see <link xlink:href="https://exist-db.org/exist/apps/doc/repo.xml#D1.4.10"/>.)</para>
+                collection.xconf file into the target location; see <link xlink:href="repo#D1.4.10"/>.)</para>
         </sect2>
 
         <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
@@ -709,7 +710,7 @@
                 <para>Create an XQuery module to centralize some of the common code and reduce
                     duplication and then reference these functions in each of your queries. For
                     example, you could put the HTML boilerplate into a style module. You could also
-                    explore eXist's HTML templating module; see <link xlink:href="https://exist-db.org/exist/apps/doc/templating.xml"/>.</para>
+                    explore eXist's <link xlink:href="templating">HTML templating module</link>.</para>
             </listitem>
             <listitem>
                 <para>Change the <code>list-items.xq</code> to use HTML tables to view each
@@ -769,7 +770,7 @@
             <listitem>
                 <para>Modify the collection configuration file for the
                     <code>/db/apps/terms/data</code> collection to enable versioning when items are
-                    updated. See <link xlink:href="https://exist-db.org/exist/apps/doc/versioning.xml"/>.</para>
+                    updated. See <link xlink:href="versioning">Versioning Extensions</link>.</para>
             </listitem>
         </orderedlist>
     </sect1>

src/main/xar-resources/data/configuration/configuration.xml

@@ -5,7 +5,7 @@
     xmlns:xlink="http://www.w3.org/1999/xlink">
     <info>
         <title>Application Server Configuration</title>
-        <date>1Q18</date>
+        <date>2Q19</date>
         <keywordset>
             <keyword>operations</keyword>
         </keywordset>
@@ -423,7 +423,7 @@
                 <title> <tag>db-connection</tag>/<tag>default-permissions</tag> element</title>
 
                 <para>Specifies the default permissions for all resources and collections in eXist
-                    (see <link xlink:href="security.xml"> User Authentication and Access
+                    (see <link xlink:href="security">User Authentication and Access
                     Control</link>). When this is not configured, the default <literal>mod</literal>
                     (similar to the Unix <code>chmod</code> command) is set to
                     <literal>0775</literal> in the <literal>resources</literal> and
@@ -463,7 +463,7 @@
                                     workaround, which will be removed in the future. Please use the
                                     n-gram or full-text indexes for case-insensitive queries or - if
                                     that is impossible - specify a <link
-                                    xlink:href="xquery.xml#collations">collation</link>.</para>
+                                    xlink:href="xquery#collations">collation</link>.</para>
                             </warning>
                         </listitem>
                     </varlistentry>
@@ -574,7 +574,7 @@
                     <literal>class</literal> and <literal>id</literal>. The other attributes, as
                     well as any nested elements, are specific to the index implementation. Detailed
                     information is available in the article on <link
-                    xlink:href="indexing.xml#moduleconf">Configuring Database Indexes</link>.</para>
+                    xlink:href="indexing#moduleconf">Configuring Database Indexes</link>.</para>
             </sect3>
 
             <sect3 xml:id="indexer-stopwords">
@@ -594,7 +594,7 @@
                 <para>Configuring indexes via the default settings is <emphasis>not</emphasis>
                     recommended. If you need a global collection configuration, store one for the
                     root collection <literal>/db</literal>. For more information, see <link
-                    xlink:href="indexing.xml">Configuring Indexes</link>.</para>
+                    xlink:href="indexing">Configuring Indexes</link>.</para>
             </sect3>
         </sect2>
 
@@ -735,7 +735,7 @@
             <para>The serializer is responsible for serializing XML documents or document fragments
                 back into XML. This configuration element defines default settings for various
                 parameters, which can also be specified programmatically. All settings can be
-                overwritten by XQuery <link xlink:href="xquery.xml#serialization">serialization
+                overwritten by XQuery <link xlink:href="xquery#serialization">serialization
                 options</link>.</para>
             <sect3 xml:id="serializer-att">
                 <title> <tag>serializer</tag> attributes</title>
@@ -821,7 +821,7 @@
                 catalog files. Catalog files are used to locate DTDs, schemas and resolve external
                 entities in general.</para>
             <para>Please refer to the corresponding documentation on <link
-                xlink:href="validation.xml">XML Validation</link>.</para>
+                xlink:href="validation">XML Validation</link>.</para>
         </sect2>
 
         <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
@@ -990,7 +990,7 @@
                     which must point to the XQuery source code of the module, for instance:</para>
                 <programlisting language="xml"><![CDATA[&amp;lt;module uri="http://exist-db.org/xquery/kwic" src="resource:org/exist/xquery/lib/kwic.xql"/&amp;gt;]]></programlisting>
                 <para>For the <code>src</code> attribute, eXist understands the <link
-                    xlink:href="xquery.xml#module-system">same types of URIs</link> as in an
+                    xlink:href="xquery#module-system">same types of URIs</link> as in an
                     ordinary XQuery import statement.</para>
             </sect3>
         </sect2>

src/main/xar-resources/data/dashboard/dashboard.xml

@@ -5,7 +5,7 @@
     xmlns:xlink="http://www.w3.org/1999/xlink">
     <info>
         <title>Dashboard</title>
-        <date>1Q18</date>
+        <date>2Q19</date>
         <keywordset>
             <keyword>getting-started</keyword>
         </keywordset>
@@ -180,6 +180,6 @@
     <para>[To be completed...]</para>
     <para>Plugins are loaded and unloaded on demand via dojo's AMD loader. They are modular, self-contained units. To add a new plugin, you need to
       provide an HTML and a <literal>.js</literal> file, which defines a subclass of the base plugin class. The source code for the dashboard is
-      available on <link  xlink:href="http://github.com/eXist-db/dashboard">GitHub</link>.</para>
+      available on <link xlink:href="https://github.com/eXist-db/dashboard">GitHub</link>.</para>
   </sect1>-->
 </article>

src/main/xar-resources/data/development-starter/development-starter.xml

@@ -5,7 +5,7 @@
     xmlns:xlink="http://www.w3.org/1999/xlink">
     <info>
         <title>Getting Started with Web Application Development</title>
-        <date>1Q18</date>
+        <date>2Q19</date>
         <keywordset>
             <keyword>getting-started</keyword>
             <keyword>application-development</keyword>
@@ -30,7 +30,7 @@
                 eXide.</para>
         </listitem>
         <listitem>
-            <para>An <link xlink:href="templating.xml">HTML templating framework</link> for a clean
+            <para>An <link xlink:href="templating">HTML templating framework</link> for a clean
                 separation of HTML page content and application logic.</para>
         </listitem>
         <listitem>

src/main/xar-resources/data/extensions/extensions.xml

@@ -327,7 +327,7 @@
             <para>Various functions for <link
                     xlink:href="http://www.opengeospatial.org/standards/gml">GML</link> geometries,
                 whether indexed or not. More information about the design is available <link
-                    xlink:href="devguide_indexes.xml">here</link>.</para>
+                    xlink:href="devguide_indexes">Developer's Guide to Modularized Indexes</link>.</para>
             <itemizedlist>
                 <listitem>
                     <para>Creator: Pierrick Brihaye</para>

src/main/xar-resources/data/getting-help/getting-help.xml

@@ -3,7 +3,7 @@
         schematypens="http://purl.oclc.org/dsdl/schematron"?><article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
   <info>
     <title>Getting Help</title>
-    <date>1Q18</date>
+    <date>2Q19</date>
     <keywordset>
       <keyword>getting-started</keyword>
     </keywordset>
@@ -18,7 +18,7 @@
   <sect1 xml:id="community-support">
     <title>Community Support</title>
 
-    <para>Besides eXist-db's extensive <link xlink:href="documentation">documentation set</link>, eXist-db has a large and active community of users
+    <para>Besides eXist-db's extensive <link xlink:href="documentation">documentation</link>, eXist-db has a large and active community of users
       and developers. The community uses mailing lists, chat, a wiki, and social media to get and give help, follow the latest developments and share
       tips and discoveries.</para>
     <para>The book, "eXist: a NoSQL Document Database and Application Platform" was published in 2014 and is available from <link xlink:href="http://shop.oreilly.com/product/0636920026525.do" condition="_blank">O'Reilly.com</link>.</para>
@@ -35,7 +35,7 @@
       question that you can't find the answer to, or you just want to join the discussion, <link xlink:href="https://lists.sourceforge.net/lists/listinfo/exist-open" condition="_blank">subscribe to the mailing list</link>. It's free and
       you can unsubscribe anytime.</para>
     <note>
-      <para>Please <link xlink:href="getting-help-how-to-report.xml">consult this page</link> for tips how to best report issues.</para>
+      <para>For reporting issues, please consult the <link xlink:href="getting-help-how-to-report">How to Report Issues</link> article.</para>
     </note>
     <para>Besides exist-open, there is a mailing list dedicated solely to the XQuery language: the <link xlink:href="http://x-query.com/mailman/listinfo/talk">xquery-talk mailing list</link>. It's a great place to ask questions about XQuery, from
       basic to advanced.</para>

src/main/xar-resources/data/incompatibilities/incompatibilities.xml

@@ -5,7 +5,7 @@
     xmlns:xlink="http://www.w3.org/1999/xlink">
     <info>
         <title>Known Issues when upgrading</title>
-        <date>4Q18</date>
+        <date>2Q19</date>
         <keywordset>
             <keyword>operations</keyword>
         </keywordset>
@@ -115,7 +115,7 @@
                 <para>2.2 introduces a <emphasis>new range index module</emphasis>. Old index
                     definitions will still work though as we made sure to keep backwards compatible.
                     If you would like to upgrade to the new index, check its <link
-                    xlink:href="newrangeindex.xml">documentation</link>.</para>
+                    xlink:href="newrangeindex">documentation</link>.</para>
             </listitem>
             <listitem>
                 <para>The XQuery engine has been updated to support the changed syntax for
@@ -267,7 +267,7 @@
                         <para>The previous <literal>auto</literal> setting was apparently too
                             confusing for new users who did not know what to do if eXist-db refused
                             to store a document due to failing validation. If you are familiar with
-                            <link xlink:href="validation.xml">validation</link>, the use of catalog
+                            <link xlink:href="validation">validation</link>, the use of catalog
                             files and the like, feel free to set the default back to
                             <literal>auto</literal> or <literal>yes</literal>.</para>
                     </listitem>
@@ -277,7 +277,7 @@
                     <listitem>
                         <para>eXist-db does no longer require Cocoon for viewing documentation and
                             samples. Cocoon has been largely replaced by eXist-db's own <link
-                            xlink:href="urlrewrite.xml">URL rewriting and MVC
+                            xlink:href="urlrewrite">URL rewriting and MVC
                             framework</link>.</para>
                         <para>Consequently, we now limit Cocoon to one directory of the web
                             application (<literal>webapp/cocoon</literal>) and moved all the Cocoon

src/main/xar-resources/data/indexing/indexing.xml

@@ -45,35 +45,35 @@
                     <code>fn:id()</code>. </para>
             </listitem>
             <listitem>
-                <para> <emphasis> <link xlink:href="newrangeindex.xml">New Range Indexes</link>
+                <para> <emphasis> <link xlink:href="newrangeindex">New Range Indexes</link>
                     </emphasis>: A (rewritten) range index which provides superior performance on
                     large data sets.</para>
             </listitem>
             <listitem>
-                <para> <emphasis> <link xlink:href="lucene.xml">Full Text Indexes</link>
+                <para> <emphasis> <link xlink:href="lucene">Full Text Indexes</link>
                     </emphasis>: This full text indexing module features faster and customizable
                     full text indexing by transparently integrating Lucene into the XQuery engine.
                     Prefer this index over the Legacy Full Text Index. </para>
             </listitem>
             <listitem>
-                <para> <emphasis> <link xlink:href="ngram.xml">NGram Indexes</link> </emphasis>:
+                <para> <emphasis> <link xlink:href="ngram">NGram Indexes</link> </emphasis>:
                     These map specific text nodes and attributes of the documents in a collection to
                     splitted tokens of n-characters (where n = 3 by default). This is very efficient
                     for exact substring searches and for queries on scripts (mostly non-European
                     ones) which can not be easily split into whitespace separated tokens and are
                     therefore a bad match for the Lucene full text index. </para>
             </listitem>
             <listitem>
-                <para> <emphasis> <link xlink:href="oldrangeindex.xml">Legacy Range Indexes</link>
+                <para> <emphasis> <link xlink:href="oldrangeindex">Legacy Range Indexes</link>
                     </emphasis>: These map specific text nodes and attributes of documents in a
                     collection to typed values.</para>
             </listitem>
             <listitem>
-                <para> <emphasis> <link xlink:href="devguide_indexes.xml#spatial">Spatial
+                <para> <emphasis> <link xlink:href="devguide_indexes#spatial">Spatial
                     Indexes</link> (Experimental)</emphasis>: A working proof-of-concept index,
                     which listens for spatial geometries described through the Geography Markup
                     Language (GML). A detailed description of the implementation can be found in the
-                    <link xlink:href="devguide_indexes.xml#spatial">Developer's Guide to Modularized
+                    <link xlink:href="devguide_indexes#spatial">Developer's Guide to Modularized
                     Indexes</link>.</para>
             </listitem>
         </orderedlist>