target.database.document.xml 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. <refentry xmlns="http://docbook.org/ns/docbook"
  2. xmlns:xlink="http://www.w3.org/1999/xlink"
  3. xmlns:xi="http://www.w3.org/2001/XInclude"
  4. xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"
  5. xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  6. version="5.0" xml:id="target.database.document">
  7. <refmeta>
  8. <refentrytitle>target.database.document</refentrytitle>
  9. <refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
  10. </refmeta>
  11. <refnamediv>
  12. <refname>target.database.document</refname>
  13. <refpurpose>Name of master database file for resolving
  14. olinks</refpurpose>
  15. </refnamediv>
  16. <refsynopsisdiv>
  17. <src:fragment xml:id="target.database.document.frag">
  18. <xsl:param name="target.database.document">olinkdb.xml</xsl:param>
  19. </src:fragment>
  20. </refsynopsisdiv>
  21. <refsection><info><title>Description</title></info>
  22. <para>
  23. To resolve olinks between documents, the stylesheets use a master
  24. database document that identifies the target datafiles for all the
  25. documents within the scope of the olinks. This parameter value is the
  26. URI of the master document to be read during processing to resolve
  27. olinks. The default value is <filename>olinkdb.xml</filename>.</para>
  28. <para>The data structure of the file is defined in the
  29. <filename>targetdatabase.dtd</filename> DTD. The database file
  30. provides the high level elements to record the identifiers, locations,
  31. and relationships of documents. The cross reference data for
  32. individual documents is generally pulled into the database using
  33. system entity references or XIncludes. See also
  34. <parameter>targets.filename</parameter>. </para> </refsection>
  35. </refentry>