|
448 | 448 | <varlistentry> |
449 | 449 | <term><xquery></term> |
450 | 450 | <listitem> |
451 | | - <para>Define modules that contain xQuery functions.</para> |
| 451 | + <para>Define (built-in) modules that contain xQuery functions.</para> |
452 | 452 | </listitem> |
453 | 453 | </varlistentry> |
454 | 454 | <varlistentry> |
|
462 | 462 | <section> |
463 | 463 | <title><db-connection></title> |
464 | 464 | <para>This element contains basic default storage settings for eXist-db, including |
465 | | - memory and system limits. Only one <sgmltag>db-connection</sgmltag> should be |
| 465 | + memory and system limits. Only one <db-connection> should be |
466 | 466 | specified. An example configuration for the native back-end is shown |
467 | 467 | below:</para> |
468 | 468 | <example> |
|
647 | 647 | shutdown due to, for example, power failures, OS reboots, and hanging |
648 | 648 | processes. For this to work correctly, all database operations must be |
649 | 649 | logged to a journal file. The location, size and other parameters for this |
650 | | - file can be set using the <sgmltag>recovery</sgmltag> element.</para> |
| 650 | + file can be set using the <recovery> element.</para> |
651 | 651 | <variablelist> |
652 | 652 | <title><recovery> Attributes</title> |
653 | 653 | <varlistentry> |
|
951 | 951 | </section> |
952 | 952 | <section> |
953 | 953 | <title> |
954 | | - <sgmltag>modules</sgmltag> |
| 954 | + <modules> |
955 | 955 | </title> |
956 | 956 | <para>This section configures optional indexing modules. Beginning with version |
957 | 957 | 1.2, eXist features a modularized indexing architecture, which allows new |
958 | 958 | indexes to be plugged into the indexing pipeline. The |
959 | | - <sgmltag>modules</sgmltag> section lists and configures the indexes that |
| 959 | + <modules> section lists and configures the indexes that |
960 | 960 | will be available to the database: </para> |
961 | 961 | <example> |
962 | 962 | <title>Configuring Index Modules</title> |
|
976 | 976 | </modules></markup> |
977 | 977 | </programlisting> |
978 | 978 | </example> |
979 | | - <para>The only common attributes for each <sgmltag>module</sgmltag> element are |
| 979 | + <para>The only common attributes for each <module> element are |
980 | 980 | <option>class</option> and <option>id</option>. The other attributes as |
981 | 981 | well as any nested elements are specific to the index implementation. |
982 | 982 | Detailed information is available in the document on <ulink url="indexing.xml#moduleconf">Configuring Database |
983 | 983 | Indexes</ulink>.</para> |
984 | 984 | </section> |
985 | 985 | <section> |
986 | 986 | <title> |
987 | | - <sgmltag>stopwords</sgmltag> |
| 987 | + <stopwords> |
988 | 988 | </title> |
989 | 989 | <para>The <option>file</option> for this element points to a file containing a |
990 | 990 | list of <emphasis>stopwords</emphasis>. Note that stopwords are |
991 | 991 | <emphasis>NOT</emphasis> added to the fullext index.</para> |
992 | 992 | </section> |
993 | 993 | <section> |
994 | 994 | <title> |
995 | | - <sgmltag>index</sgmltag> |
| 995 | + <index> |
996 | 996 | </title> |
997 | 997 | <para>This configuration element specifies the default index settings. These |
998 | 998 | settings are applied if neither the collection nor any of its ancestors |
|
1005 | 1005 | </section> |
1006 | 1006 | <section> |
1007 | 1007 | <title> |
1008 | | - <sgmltag>scheduler</sgmltag> |
| 1008 | + <scheduler> |
1009 | 1009 | </title> |
1010 | 1010 | <para>This section is used to configure asynchronous jobs with eXist's internal |
1011 | 1011 | scheduler. Three types of jobs are supported:</para> |
|
1056 | 1056 | </scheduler></markup> |
1057 | 1057 | </programlisting> |
1058 | 1058 | </example> |
1059 | | - <para>Each job is configured in a <sgmltag>job</sgmltag> element which accepts a |
| 1059 | + <para>Each job is configured in a <job> element which accepts a |
1060 | 1060 | number of standard attributes:</para> |
1061 | 1061 | <section> |
1062 | 1062 | <title> |
1063 | | - <sgmltag>job</sgmltag> attributes</title> |
| 1063 | + <job> attributes</title> |
1064 | 1064 | <variablelist> |
1065 | 1065 | <varlistentry> |
1066 | 1066 | <term>type</term> |
|
1156 | 1156 | <varlistentry> |
1157 | 1157 | <term>enable-xinclude</term> |
1158 | 1158 | <listitem> |
1159 | | - <para>This attribute determines whether <sgmltag>xinclude</sgmltag> |
| 1159 | + <para>This attribute determines whether <xinclude> |
1160 | 1160 | tags are to be expanded during serialization. Setting the value |
1161 | 1161 | to "<option>false</option>" will leave |
1162 | | - <sgmltag>xinclude</sgmltag> tags unexpanded.</para> |
| 1162 | + <xinclude> tags unexpanded.</para> |
1163 | 1163 | </listitem> |
1164 | 1164 | </varlistentry> |
1165 | 1165 | <varlistentry> |
|
1210 | 1210 | <listitem> |
1211 | 1211 | <para>The database can highlight matches in the text content of a |
1212 | 1212 | node by tagging the matching text string with |
1213 | | - <sgmltag>exist:match</sgmltag>. Clearly, this only works for |
| 1213 | + <exist:match>. Clearly, this only works for |
1214 | 1214 | XPath expressions using the fulltext index. Set the parameter to |
1215 | 1215 | "<option>yes</option>" to <emphasis>disable</emphasis> this |
1216 | 1216 | feature.</para> |
|
1221 | 1221 | </section> |
1222 | 1222 | <section> |
1223 | 1223 | <title> |
1224 | | - <sgmltag>transformer</sgmltag> |
| 1224 | + <transformer> |
1225 | 1225 | </title> |
1226 | 1226 | <para>This section determines which XSLT processor will be used by eXist. By |
1227 | 1227 | default, eXist relies on Xalan, which is an XSLT 1.0 engine. Please refer to |
|
1230 | 1230 | </section> |
1231 | 1231 | <section> |
1232 | 1232 | <title> |
1233 | | - <sgmltag>validation</sgmltag> |
| 1233 | + <validation> |
1234 | 1234 | </title> |
1235 | 1235 | <para>Defines the default validation settings that will be active when parsing XML |
1236 | 1236 | and links to catalog files. Catalog files are used to locate DTDs, schemas and |
|
1242 | 1242 | <para>Inserting new nodes into a document can lead to fragmentation in the DOM |
1243 | 1243 | storage file. eXist will thus trigger a defragmentation run if the fragmentation |
1244 | 1244 | exceeds a certain limit. The frequency of such defragmentation runs can be |
1245 | | - configured in the <sgmltag>xupdate</sgmltag> section. The main parameter is |
| 1245 | + configured in the <xupdate> section. The main parameter is |
1246 | 1246 | called <option>allowed-fragmentation</option>:</para> |
1247 | 1247 | <example> |
1248 | 1248 | <title>XUpdate-Options in conf.xml</title> |
|
1278 | 1278 | </section> |
1279 | 1279 | <section> |
1280 | 1280 | <title> |
1281 | | - <sgmltag>xquery</sgmltag> |
| 1281 | + <xquery> |
1282 | 1282 | </title> |
1283 | 1283 | <example> |
1284 | 1284 | <title>XQuery Engine Configuration</title> |
|
1293 | 1293 | </xquery></markup> |
1294 | 1294 | </programlisting> |
1295 | 1295 | </example> |
1296 | | - <para>The <sgmltag>xquery</sgmltag> section is used to enable/disable certain core |
| 1296 | + <para>The <xquery> section is used to enable/disable certain core |
1297 | 1297 | features of the XQuery engine. It also lists the XQuery modules that will be |
1298 | 1298 | known to the query engine by default.</para> |
1299 | 1299 | <section> |
1300 | 1300 | <title> |
1301 | | - <sgmltag>xquery</sgmltag> attributes</title> |
| 1301 | + <xquery> attributes</title> |
1302 | 1302 | <variablelist> |
1303 | 1303 | <varlistentry> |
1304 | 1304 | <term>enable-java-binding=yes|no</term> |
|
1327 | 1327 | the entire collection set.</para> |
1328 | 1328 | <para>For example, if you have two collections: /db/one and /db/two, |
1329 | 1329 | and you define a range index on a certain element |
1330 | | - <sgmltag>node</sgmltag> in /db/one, but not in /db/two, the |
| 1330 | + <node> in /db/one, but not in /db/two, the |
1331 | 1331 | query engine would not use the index with setting "strict" if |
1332 | 1332 | you query both collections. At compile time, eXist doesn't know |
1333 | | - if <sgmltag>node</sgmltag> exists in both collections and will |
| 1333 | + if <node> exists in both collections and will |
1334 | 1334 | not use the index if it determines that an index definition does |
1335 | 1335 | only apply to a part of the collection set being queried. To use |
1336 | 1336 | the index, you would need to start your XPath expression with a |
|
1391 | 1391 | </variablelist> |
1392 | 1392 | </section> |
1393 | 1393 | <section> |
1394 | | - <title> |
1395 | | - <sgmltag>builtin-modules</sgmltag> |
| 1394 | + <title><builtin-modules> |
1396 | 1395 | </title> |
1397 | 1396 | <para>This section lists the XQuery modules which will be known to the query |
1398 | 1397 | engine. The modules in this list can be imported into a query without |
|
0 commit comments