What does this package do? (explain in 50 words or less): Transform Ecological Metadata Language (EML) files into JSON-LD and back into EML. Doing so creates a natural list-based representation of EML in R, so that EML data can easily be manipulated using standard R tools. This makes this package an effective backend for other tools for working with EML. Additioally, the JSON-LD representation enables the use of developer-friendly JSON parsing and informatics-friendly serializations such as RDF and SPARQL queries. This package is targeted primarily at developers. By abstracting away the complexity of EML’s XML Schema, developers can build against intuitive list or JSON objects and not have to worry about satisfying many of the additional constraints of set by the schema (such as element ordering, which is handled automatically).
In practice, `emld` will basically be the backend machinery for a new release of the `EML`
package, which will retain largely the same user-facing API, with several improvements.
But both in terms of ease of reviewing and ease of package maintenance, I think it's important
to have these as separate packages.
Paste the full DESCRIPTION file inside a code block below:
Package: emld
Title: Ecological Metadata as Linked Data
Version: 0.0.2
Authors@R: person("Carl", "Boettiger",
email = "cboettig@gmail.com",
role = c("aut", "cre", "cph"),
comment=c(ORCID = "http://orcid.org/0000-0002-1642-628X"))
Description: Transform Ecological Metadata Language (EML) files into JSON-LD
and back into EML. Doing so creates a natural list-based representation
of EML in R, so that EML data can easily be manipulated using standard
R tools. This makes this package an effective backend for other tools
for working with EML. Additioally, the JSON-LD representation enables
the use of developer-friendly JSON parsing and informatics-friendly
serializations such as RDF and SPARQL queries. This package is targeted
primarily at developers. By abstracting away the complexity of EML's
XML Schema, developers can build against intuitive list or JSON objects
and not have to worry about satisfying many of the additional constraints
of set by the schema (such as element ordering, which is handled automatically).
URL: https://github.com/cboettig/emld
BugReports: https://github.com/cboettig/emld/issues
Depends: R (>= 3.1.0)
License: MIT + file LICENSE
Encoding: UTF-8
LazyData: true
RoxygenNote: 6.1.1
Suggests:
spelling,
testthat,
magrittr,
rmarkdown,
covr,
knitr,
rdflib,
jqr
Imports: xml2,
jsonlite,
jsonld,
methods,
yaml
VignetteBuilder: knitr
Language: en-US
URL for the package (the development repository, not a stylized html page): https://github.com/cboettig/emld
Please indicate which category or categories from our package fit policies this package falls under *and why(? (e.g., data retrieval, reproducibility. If you are unsure, we suggest you make a pre-submission inquiry.):
data publication, data retrieval, and reproducibility.
Researchers and ecological informatics teams (at NEON, LTER sites, NCEAS, etc) who are consuming or managing EML and data described by EML.
This overlaps with the EML
package, and will soon be the backend to the newer version of said package. This package works very differently than the current CRAN version of EML: instead of a massive S4 class system, this uses a single S3 class by exploiting the magic of JSON-LD.
Confirm each of the following by checking the box. This package:
paper.md
matching JOSS’s requirements with a high-level description in the package root or in inst/
.x ] Does R CMD check
(or devtools::check()
) succeed? Paste and describe any errors or warnings:
[x] Does the package conform to rOpenSci packaging guidelines? Please describe any exceptions:
If this is a resubmission following rejection, please explain the change in circumstances:
If possible, please provide recommendations of reviewers - those with experience with similar packages and/or likely users of your package - and their GitHub user names: