EVOLUTION-MANAGER
Edit File: newXMLDoc.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: Create internal XML node or document object</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 newXMLDoc {XML}"><tr><td>newXMLDoc {XML}</td><td style="text-align: right;">R Documentation</td></tr></table> <h2>Create internal XML node or document object</h2> <h3>Description</h3> <p>These are used to create internal ‘libxml’ nodes and top-level document objects that are used to write XML trees. While the functions are available, their direct use is not encouraged. Instead, use <code><a href="xmlTree.html">xmlTree</a></code> as the functions need to be used within a strict regime to avoid corrupting C level structures. </p> <p><code>xmlDoc</code> creates a new XMLInternalDocument object by copying the given node and all of its descendants and putting them into a new document. This is useful when we want to work with sub-trees with general tools that work on documents, e.g. XPath queries. </p> <p><code>newXMLDoc</code> allows one to create a regular XML node with a name and attributes. One can provide new namespace definitions via <code>namespaceDefinitions</code>. While these might also be given in the attributes in the slightly more verbose form of <code>c('xmlns:prefix' = 'http://...')</code>, the result is that the XML node does not interpret that as a namespace definition but merely an attribute with a name 'xmlns:prefix'. Instead, one should specify the namespace definitions via the <code>namespaceDefinitions</code> parameter. </p> <p>In addition to namespace definitions, a node name can also have a namespace definition. This can be specified in the <code>name</code> argument as <code>prefix:name</code> and <code>newXMLDoc</code> will do the right thing in separating this into the namespace and regular name. Alternatively, one can specify a namespace separately via the <code>namespace</code> argument. This can be either a simple name or an internal namespace object defined earlier. </p> <p>How do we define a default namespace? </p> <h3>Usage</h3> <pre> xmlDoc(node, addFinalizer = TRUE) newXMLDoc(dtd = "", namespaces=NULL, addFinalizer = TRUE, name = character(), node = NULL, isHTML = FALSE) newHTMLDoc(dtd = "loose", addFinalizer = TRUE, name = character(), node = newXMLNode("html", newXMLNode("head", addFinalizer = FALSE), newXMLNode("body", addFinalizer = FALSE), addFinalizer = FALSE)) newXMLNode(name, ..., attrs = NULL, namespace = character(), namespaceDefinitions = character(), doc = NULL, .children = list(...), parent = NULL, at = NA, cdata = FALSE, suppressNamespaceWarning = getOption("suppressXMLNamespaceWarning", FALSE), sibling = NULL, addFinalizer = NA, noNamespace = length(namespace) == 0 && !missing(namespace), fixNamespaces = c(dummy = TRUE, default = TRUE)) newXMLTextNode(text, parent = NULL, doc = NULL, cdata = FALSE, escapeEntities = is(text, "AsIs"), addFinalizer = NA) newXMLCDataNode(text, parent = NULL, doc = NULL, at = NA, sep = "\n", addFinalizer = NA) newXMLCommentNode(text, parent = NULL, doc = NULL, at = NA, addFinalizer = NA) newXMLPINode(name, text, parent = NULL, doc = NULL, at = NA, addFinalizer = NA) newXMLDTDNode(nodeName, externalID = character(), systemID = character(), doc = NULL, addFinalizer = NA) </pre> <h3>Arguments</h3> <table summary="R argblock"> <tr valign="top"><td><code>node</code></td> <td> <p>a <code>XMLInternalNode</code> object that will be copied to create a subtree for a new document.</p> </td></tr> <tr valign="top"><td><code>dtd</code></td> <td> <p>the name of the DTD to use for the XML document. Currently ignored!</p> </td></tr> <tr valign="top"><td><code>namespaces</code></td> <td> <p>a named character vector with each element specifying a name space identifier and the corresponding URI for that namespace that are to be declared and used in the XML document, \ e.g. <code>c(shelp = "http://www.omegahat.net/XML/SHelp")</code></p> </td></tr> <tr valign="top"><td><code>addFinalizer</code></td> <td> <p>a logical value indicating whether the default finalizer routine should be registered to free the internal xmlDoc when R no longer has a reference to this external pointer object. This can also be the name of a C routine or a reference to a C routine retrieved using <code><a href="../../base/html/getNativeSymbolInfo.html">getNativeSymbolInfo</a></code>. </p> </td></tr> <tr valign="top"><td><code>name</code></td> <td> <p>the tag/element name for the XML node and the for a Processing Instruction (PI) node, this is the "target", e.g. the identifier for the system for whose attention this PI node is intended.</p> </td></tr> <tr valign="top"><td><code>...</code></td> <td> <p>the children of this node. These can be other nodes created earlier or R strings that are converted to text nodes and added as children to this newly created node.</p> </td></tr> <tr valign="top"><td><code>attrs</code></td> <td> <p>a named list of name-value pairs to be used as attributes for the XML node. One should not use this argument to define namespaces, i.e. attributes of the form <code>xmlns:prefix='http:/...'</code>. Instead, such definitions should be specified ideally via the <code>namespaceDefinitions</code> argument, or even the <code>namespace</code> argument. The reason is that namespace definitions are special attributes that are shared across nodes wherease regular attributes are particular to a node. So a namespace needs to be explicitly defined so that the XML representation can recognize it as such. </p> </td></tr> <tr valign="top"><td><code>namespace</code></td> <td> <p>a character vector specifying the namespace for this new node. Typically this is used to specify i) the prefix of the namespace to use, or ii) one or more namespace definitions, or iii) a combination of both. If this is a character vector with a) one element and b) with an empty <code>names</code> attribute and c) whose value does not start with <code>http:/</code> or <code>ftp:/</code>, then it is assumed that the value is a namespace prefix for a namespace defined in an ancestor node. To be able to resolve this prefix to a namespace definition, <code>parent</code> must be specified so that we can traverse the chain of ancestor nodes. However, if c) does not hold, i.e. the string starts with <code>http:/</code> or <code>ftp:/</code>, then we take this single element to be a namespace definition and the since it has no name b), this is the definition for the default namespace for this new node, i.e. corresponding to <code>xmlns='http:/...'</code>. It is cumbersome to specify <code>""</code> as a name for an element in a character vector (as <code>c('' = 'value') gives an unnecessary error!</code>. Elements with names are expanded to namespace definitions with the name as the prefix and the value as the namespace URI. </p> </td></tr> <tr valign="top"><td><code>doc</code></td> <td> <p>the <code>XMLInternalDocument</code> object created with <code>newXMLDoc</code> that is used to root the node.</p> </td></tr> <tr valign="top"><td><code>.children</code></td> <td> <p>a list containing XML node elements or content. This is an alternative form of specifying the child nodes than ... which is useful for programmatic interaction when the "sub"-content is already in a list rather than a loose collection of values.</p> </td></tr> <tr valign="top"><td><code>text</code></td> <td> <p>the text content for the new XML node</p> </td></tr> <tr valign="top"><td><code>nodeName</code></td> <td> <p>the name of the node to put in the DOCTYPE element that will appear as the top-most node in the XML document.</p> </td></tr> <tr valign="top"><td><code>externalID</code></td> <td> <p>the PUBLIC identifier for the document type. This is a string of the form <code>A//B//C//D</code>. A is either + or -; B identifies the person or insitution that defined the format (i.e. the "creator"); C is the name of the format; and language is an encoding for the language that comes from the ISO 639 document.</p> </td></tr> <tr valign="top"><td><code>systemID</code></td> <td> <p>the SYSTEM identifier for the DTD for the document. This is a URI</p> </td></tr> <tr valign="top"><td><code>namespaceDefinitions</code></td> <td> <p>a character vector or a list with each element being a string. These give the URIs identifying the namespaces uniquely. The elements should have names which are used as prefixes. A default namespace has "" as the name. This argument can be used to remove any ambiguity that arises when specifying a single string with no names attribute as the value for <code>namespace</code>. The values here are used only for defining new namespaces and not for determining the namespace to use for this particular node. </p> </td></tr> <tr valign="top"><td><code>parent</code></td> <td> <p>the node which will act as the parent of this newly created node. This need not be specified and one can add the new node to another node in a separate operation via <code><a href="addChildren.html">addChildren</a></code>.</p> </td></tr> <tr valign="top"><td><code>sibling</code></td> <td> <p>if this is specified (rather than <code>parent</code>) this should be an <code>XMLInternalNode</code> and the new node is added as a sibling of this node, after this node, i.e. to the right. This is just a convenient form of <code>parent = xmlParent(node)</code>.</p> </td></tr> <tr valign="top"><td><code>cdata</code></td> <td> <p>a logical value indicating whether to enclose the text within a CDATA node (<code>TRUE</code>) or not (<code>FALSE</code>). This is a convenience mechanism to avoid having to create the text node and then the CDATA node. If one is not certain what characters are in the text, it is useful to use <code>TRUE</code> to ensure that they are “escaped”. </p> <p>It is an argument for <code>newXMLNode</code> as the child nodes can be given as simple strings and are converted to text nodes. This <code>cdata</code> value is passed to the calls to create these text nodes and so controls whether they are enclosed within CDATA nodes. </p> </td></tr> <tr valign="top"><td><code>suppressNamespaceWarning</code></td> <td> <p>see <code><a href="addChildren.html">addChildren</a></code></p> </td></tr> <tr valign="top"><td><code>at</code></td> <td> <p>this allows one to control the position in the list of children at which the node should be added. The default means at the end and this can be any position from 0 to the current number of children.</p> </td></tr> <tr valign="top"><td><code>sep</code></td> <td> <p>when adding text nodes, this is used as an additional separator text to insert between the specified strings.</p> </td></tr> <tr valign="top"><td><code>escapeEntities</code></td> <td> <p>a logical value indicating whether to mark the internal text node in such a way that protects characters in its contents from being escaped as entities when being serialized via <code><a href="saveXML.html">saveXML</a></code></p> </td></tr> <tr valign="top"><td><code>noNamespace</code></td> <td> <p>a logical value that allows the caller to specify that the new node has no namespace. This can avoid searching parent and ancestor nodes up the tree for the default namespace.</p> </td></tr> <tr valign="top"><td><code>isHTML</code></td> <td> <p>a logical value that indicates whether the XML document being created is HTML or generic XML. This helps to create an object that is identified as an HTML document.</p> </td></tr> <tr valign="top"><td><code>fixNamespaces</code></td> <td> <p>a logical vector controlling how namespaces in child nodes are to be processed. The two entries should be named <code>dummy</code> and <code>default</code>. The <code>dummy</code> element controls whether we process child nodes that have a namespace which was not defined when the node was created. These are created as “dummy” namespaces and can be resolved now that the parent node is defined and the name space may be defined. When we know it is not yet defined, but will be defined in an ancestor node, we can turn off this processing with a value of <code>FALSE</code>. </p> <p>The <code>default</code> element controls how we process the child nodes and give them the default name space defined in the parent or ancestor nodes.</p> </td></tr> </table> <h3>Details</h3> <p>These create internal C level objects/structure instances that can be added to a libxml DOM and subsequently inserted into other document objects or “serialized” to textual form. </p> <h3>Value</h3> <p>Each function returns an R object that points to the C-level structure instance. These are of class <code>XMLInternalDocument</code> and <code>XMLInternalNode</code>, respectively </p> <h3>Note</h3> <p>These functions are used to build up an internal XML tree. This can be used in the Sxslt package (<a href="http://www.omegahat.net/Sxslt">http://www.omegahat.net/Sxslt</a>) when creating content in R that is to be dynamically inserted into an XML document.</p> <h3>Author(s)</h3> <p> Duncan Temple Lang </p> <h3>References</h3> <p><a href="http://www.w3.org/XML">http://www.w3.org/XML</a>, <a href="http://www.xmlsoft.org">http://www.xmlsoft.org</a>, <a href="http://www.omegahat.net">http://www.omegahat.net</a></p> <h3>See Also</h3> <p><code><a href="xmlTree.html">xmlTree</a></code> <code>saveXML</code> </p> <h3>Examples</h3> <pre> doc = newXMLDoc() # Simple creation of an XML tree using these functions top = newXMLNode("a") newXMLNode("b", attrs = c(x = 1, y = 'abc'), parent = top) newXMLNode("c", "With some text", parent = top) d = newXMLNode("d", newXMLTextNode("With text as an explicit node"), parent = top) newXMLCDataNode("x <- 1\n x > 2", parent = d) newXMLPINode("R", "library(XML)", top) newXMLCommentNode("This is a comment", parent = top) o = newXMLNode("ol", parent = top) kids = lapply(letters[1:3], function(x) newXMLNode("li", x)) addChildren(o, kids) cat(saveXML(top)) x = newXMLNode("block", "xyz", attrs = c(id = "bob"), namespace = "fo", namespaceDefinitions = c("fo" = "http://www.fo.org")) xmlName(x, TRUE) == "fo" # a short cut to define a name space and make it the prefix for the # node, thus avoiding repeating the prefix via the namespace argument. x = newXMLNode("block", "xyz", attrs = c(id = "bob"), namespace = c("fo" = "http://www.fo.org")) # name space on the attribute x = newXMLNode("block", attrs = c("fo:id" = "bob"), namespaceDefinitions = c("fo" = "http://www.fo.org")) x = summary(rnorm(1000)) d = xmlTree() d$addNode("table", close = FALSE) d$addNode("tr", .children = sapply(names(x), function(x) d$addNode("th", x))) d$addNode("tr", .children = sapply(x, function(x) d$addNode("td", format(x)))) d$closeNode() # Just doctype z = xmlTree("people", dtd = "people") # no public element z = xmlTree("people", dtd = c("people", "", "http://www.omegahat.net/XML/types.dtd")) # public and system z = xmlTree("people", dtd = c("people", "//a//b//c//d", "http://www.omegahat.net/XML/types.dtd")) # Using a DTD node directly. dtd = newXMLDTDNode(c("people", "", "http://www.omegahat.net/XML/types.dtd")) z = xmlTree("people", dtd = dtd) x = rnorm(3) z = xmlTree("r:data", namespaces = c(r = "http://www.r-project.org")) z$addNode("numeric", attrs = c("r:length" = length(x)), close = FALSE) lapply(x, function(v) z$addNode("el", x)) z$closeNode() # should give <r:data><numeric r:length="3"/></r:data> # shows namespace prefix on an attribute, and different from the one on the node. z = xmlTree() z$addNode("r:data", namespace = c(r = "http://www.r-project.org", omg = "http://www.omegahat.net"), close = FALSE) x = rnorm(3) z$addNode("r:numeric", attrs = c("omg:length" = length(x))) z = xmlTree("people", namespaces = list(r = "http://www.r-project.org")) z$setNamespace("r") z$addNode("person", attrs = c(id = "123"), close = FALSE) z$addNode("firstname", "Duncan") z$addNode("surname", "Temple Lang") z$addNode("title", "Associate Professor") z$addNode("expertize", close = FALSE) z$addNode("topic", "Data Technologies") z$addNode("topic", "Programming Language Design") z$addNode("topic", "Parallel Computing") z$addNode("topic", "Data Visualization") z$closeTag() z$addNode("address", "4210 Mathematical Sciences Building, UC Davis") # txt = newXMLTextNode("x &lt; 1") txt # okay saveXML(txt) # x &amp;lt; 1 # By escaping the text, we ensure the entities don't # get expanded, i.e. &lt; doesn't become &amp;lt; txt = newXMLTextNode(I("x &lt; 1")) txt # okay saveXML(txt) # x &lt; 1 newXMLNode("r:expr", newXMLTextNode(I("x < 1")), namespaceDefinitions = c(r = "http://www.r-project.org")) </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>