EVOLUTION-MANAGER
Edit File: catalogs.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>R: Manipulate XML catalog contents</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <link rel="stylesheet" type="text/css" href="R.css" /> </head><body> <table width="100%" summary="page for catalogLoad {XML}"><tr><td>catalogLoad {XML}</td><td style="text-align: right;">R Documentation</td></tr></table> <h2>Manipulate XML catalog contents</h2> <h3>Description</h3> <p>These functions allow the R user to programmatically control the XML catalog table used in the XML parsing tools in the C-level libxml2 library and hence in R packages that use these, e.g. the XML and Sxslt packages. Catalogs are consulted whenever an external document needs to be loaded. XML catalogs allow one to influence how such a document is loaded by mapping document identifiers to alternative locations, for example to refer to locally available versions. They support mapping URI prefixes to local file directories/files, resolving both SYSTEM and PUBLIC identifiers used in DOCTYPE declarations at the top of an XML/HTML document, and delegating resolution to other catalog files. Catalogs are written using an XML format. </p> <p>Catalogs allow resources used in XInclude nodes and XSL templates to refer to generic network URLs and have these be mapped to local files and so avoid potentially slow network retrieval. Catalog files are written in XML We might have a catalog file that contains the XML In the XDynDocs package, we refer to OmegahatXSL files and DocBook XSL files have a catalog file of the form </p> <p>The functions provided here allow the R programmer to empty the current contents of the global catalog table and so start from scratch ( <code>catalogClearTable</code> ), load the contents of a catalog file into the global catalog table ( <code>catalogLoad</code> ), and to add individual entries programmatically without the need for a catalog table. </p> <p>In addition to controlling the catalogs via these functions, we can use <code><a href="catalogResolve.html">catalogResolve</a></code> to use the catalog to resolve the name of a resource and map it to a local resource. </p> <p><code>catalogDump</code> allows us to retrieve an XML document representing the current contents of the in-memory catalog . </p> <p>More information can be found at <a href="http://xmlsoft.org/catalog.html">http://xmlsoft.org/catalog.html</a> and <a href="http://www.sagehill.net/docbookxsl/Catalogs.html">http://www.sagehill.net/docbookxsl/Catalogs.html</a> among many resources and the specification for the catalog format at <a href="http://www.oasis-open.org/committees/entity/spec-2001-08-06.html">http://www.oasis-open.org/committees/entity/spec-2001-08-06.html</a>. </p> <h3>Usage</h3> <pre> catalogLoad(fileNames) catalogClearTable() catalogAdd(orig, replace, type = "rewriteURI") catalogDump(fileName = tempfile(), asText = TRUE) </pre> <h3>Arguments</h3> <table summary="R argblock"> <tr valign="top"><td><code>orig</code></td> <td> <p>a character vector of identifiers, e.g. URIs, that are to be mapped to a different name via the catalog. This can be a named character vector where the names are the original URIs and the values are the corresponding rewritten values. </p> </td></tr> <tr valign="top"><td><code>replace</code></td> <td> <p>a character vector of the rewritten or resolved values for the identifiers given in orig. Often this omitted and the original-rewrite pairs are given as a named vector via orig. </p> </td></tr> <tr valign="top"><td><code>type</code></td> <td> <p>a character vector with the same length as orig (or recycled to have the same length) which specifies the type of the resources in the elements of orig. Valid values are rewriteURI, rewriteSystem, system, public. </p> </td></tr> <tr valign="top"><td><code>fileNames</code></td> <td> <p>a character vector giving the names of the catalog files to load.</p> </td></tr> <tr valign="top"><td><code>fileName</code></td> <td> <p>the name of the file in which to place the contents of the current catalog</p> </td></tr> <tr valign="top"><td><code>asText</code></td> <td> <p>a logical value which indicates whether to write the catalog as a character string if <code>filename</code> is not specified.</p> </td></tr> </table> <h3>Value</h3> <p>These functions are used for their side effects on the global catalog table maintained in C by libxml2. Their return values are logical values/vectors indicating whether the particular operation were successful or not. </p> <h3>References</h3> <p>This provides an R-like interface to a small subset of the catalog API made available in libxml2. </p> <h3>See Also</h3> <p><code><a href="catalogResolve.html">catalogResolve</a></code> </p> <p>XInclude, XSL and import/include directives. </p> <p>In addition to these functions, there is an un-exported, undocumented function named <code>catalogDump</code> that can be used to get the contents of the (first) catalog table. </p> <h3>Examples</h3> <pre> # Add a rewrite rule # # catalogAdd(c("http://www.omegahat.net/XML" = system.file("XML", package = "XML"))) catalogAdd("http://www.omegahat.net/XML", system.file("XML", package = "XML")) catalogAdd("http://www.r-project.org/doc/", paste(R.home(), "doc", "", sep = .Platform$file.sep)) # # This shows how we can load a catalog and then resolve a # systemidentifier that it maps. # catalogLoad(system.file("exampleData", "catalog.xml", package = "XML")) catalogResolve("docbook4.4.dtd", "system") catalogResolve("-//OASIS//DTD DocBook XML V4.4//EN", "public") </pre> <hr /><div style="text-align: center;">[Package <em>XML</em> version 3.99-0.3 <a href="00Index.html">Index</a>]</div> </body></html>