{"Package":"xmlr","Version":"0.1.2","Date":"2020-05-06","Title":"Read, Write and Work with 'XML' Data","Authors@R":"c(\nperson(\"Per\", \"Nyfelt\", email = \"per@alipsa.se\", role = c(\"cre\", \"aut\")),\nperson(\"Alipsa HB\", email = \"info@alipsa.se\", role = \"cph\"),\nperson(\"Steven\", \"Brandt\", role = \"ctb\")\n)","Maintainer":"Per Nyfelt ","Depends":"R (>= 3.1.0)","Encoding":"UTF-8","Description":"'XML' package for creating and reading and manipulating 'XML', with an object model based on 'Reference Classes'.","License":"MIT + file LICENSE","URL":"https://github.com/Alipsa/xmlr","BugReports":"https://github.com/Alipsa/xmlr/issues","Imports":"methods","Suggests":"testthat, knitr, rmarkdown","Collate":"'xmlr.R' 'utils.R' 'AbstractClass.R' 'Content.R' 'Document.R'\n'Text.R' 'Element.R' 'Stack.R' 'DomBuilder.R' 'Parser.R'\n'xmlImporter.R' 'xmlConverter.R'","RoxygenNote":"7.1.0","VignetteBuilder":"knitr","NeedsCompilation":"no","Packaged":"2020-05-06 18:45:58 UTC; per","Author":"Per Nyfelt [cre, aut],\nAlipsa HB [cph],\nSteven Brandt [ctb]","Repository":"CRAN","Date/Publication":"2020-05-12 09:30:02 UTC","repoType":"cran","tarballUrl":"ftp://cran.r-project.org/pub/R/src/contrib/xmlr_0.1.2.tar.gz","jsonAuthors":[{"name":"Per Nyfelt","email":"per@alipsa.se","maintainer":true},{"name":"Alipsa HB ","email":"info@alipsa.se","maintainer":false},{"name":"Steven Brandt","email":null,"maintainer":false}],"readme":"# xmlr\nXML dom package for R implemented using Reference Classes\n\nThe jdom project (www.jdom.org) provided a lot of initial inspiration for the api but there are several differences, mainly \n- Attributes: Attribute is not a specific class but just a name value element of the named list property of an Element\n- Namespaces:\n Whereas in jdom namespaces is a special class that exists as a specific object attribute, xmlr takes a \"simpler\"\n approach in the sense that namespace declarations are just another element attribute and name space prefixes are part of the \n element name. This might change in the future but for now this is how it is done.\n\nYou can create and xmlr Document programmatically or by parsing text or a file. \n\n# Creating the DOM programmatically\nTo create the following xml\n```\n\n \n \n \n \n

Apples

Bananas

\n\n```\nYou could do something like this:\n```\n doc <- Document$new()\n root <- Element$new(\"table\")\n root$setAttribute(\"xmlns\", \"http://www.w3.org/TR/html4/\")\n\n root$addContent(\n Element$new(\"tr\")\n $addContent(Element$new(\"td\")$setText(\"Apples\"))\n $addContent(Element$new(\"td\")$setText(\"Bananas\"))\n )\n doc$setRootElement(root)\n```\nOr you could do like this:\n```\ndoc2 <- parse.xmlstring(\"\n\n \n \n \n \n

Apples

Bananas

\")\n```\nNote that there is no pretty print available (yet) so if you print it `print(doc2)`\nit will look like this:\n```\n> print(doc2)\n

Apples

Bananas

\n> \n```\n\n# Limitations\nProcessing instructions, custom entity references, and comments are not yet supported.\n\nAny proper xml including CDATA, comments, processing instructions etc. can be parsed though, it is just that\nonly elements, attributes and text will be retained.\n\nCDATA can be read from string or file but handled as ordinary text after that. I.e. the output might not be valid XML.\n\nThere are probably issues (memory, performance) with very large XML trees.\n\n# Why xmlr?\nI had problems on one of my machines to install the XML package (some gcc issue) so needed an alternative.\nAs I have been thinking about doing something more comprehensive with Reference Classes I decided to create\na pure base-R DOM model with some simple ways to do input and output to strings and files. As it turned out to\nbe useful to me, I thought it might be for others as well, so I decided to open source and publish it.\n\n\n\n","jobInfo":{"package":"xmlr","version":"0.1.2","parsingStatus":"success","parserVersion":1,"parsedAt":"2020-05-12T12:31:15+0000"}}

Description

Usage

Arguments

Value

Functions