function to create an eml_software node about eml HOT 4 CLOSED

The minimal version of software nodes is now written (eml_software), but really needs to be extended to support the full software node: http://knb.ecoinformatics.org/software/eml/eml-2.1.1/eml-software.png

At least the eml_R_software should be re-written as a coercion method (e.g. see as.eml_person) and extract and map all package description fields (well, except fields that don't map, like the collate list). So far we map title (actually we use packagename), authors, version, url, and license.

from eml.

What does implementation refer to (the second check box in the original issue at the top)?

from eml.

Implementation is a required child node of a software node, see: http://knb.ecoinformatics.org/software/eml/eml-2.1.1/eml-software.html

The description there explains: "Implementation describes the hardware, operating system resources a package runs on...."

The only required child node of an implementation node is the distribution node, which can be a variety of things (click through the links -- yes, you can specify carved on stone tablets)

You'll see my implementation only provides for online distribution, in which case we're required to simply give a url. e.g. the implementation node I generate for reml looks like:

         <implementation>
            <distribution>
              <online>
                <url>https://github.com/ropensci/reml</url>
              </online>
            </distribution>
          </implementation>

from eml.

As this now provides a working if not fully featured implementation, will close this issue. A better / more thorough implementation should probably use the S4 approach described in #38, (e.g. will come more-or-less for free once XMLSchema methods are ready).

from eml.