RNeXML should optionally be able to include all the basic metadata listed on the MIAPA checklist, hopefully guiding users that are unfamiliar with the process and being able to provide reasonable automated suggestions when possible (e.g. suggesting external identifiers based on OTU labels, #24) A function might be provided that could check (and perhaps summarize/return) miapa compliance(?).
I've reproduced the checklist below with notes added on how we're doing in RNeXML.
For each item, I've either made a note on if/how we handle it in NeXML, or a question when I'm unsure how to handle it. For instance, I can sometimes find a corresponding block in the example files in the miapa repo, but they are in OWL and the translation to NeXML's meta/RDFa isn't clear to me. An example nexml file that satisfies all these requirements would be super helpful to me.
Topology
[ ] The topology itself, possibly as an identifier of a database (such as a !TreeBASE) record. included in the nexml tree node
[ ] Is this a gene tree or species tree? Do we use the treebase namespace to define this, or is there a better alternative?
[ ] It is a tree or a network? nexml defines this by using <tree> or <network>
[ ] Is topology rooted or not? _In nexml, defined by an attribute root="true" on a member nod__. Should we consider declaring this in metadata too?
[ ] The type of consensus if this a consensus topology (that summarizes the topology inference in some way, rather than being directly provided by the inference method)
Do we use the treebase namespace for this as well? e.g.
[ ] The topology should be "well described", as applicable to the inference method being used. For example, a likelihood for maximum likelihood analysis. For Bayesian analyses this should also include the burn-in period excluded, and the convergence of the chain(s). This may also include more then one topology, for example a sample from the posterior probability distribution for Bayesian, or equally scoring topologies for a maximum parsimony analysis. Examples?
OTUs:
All terminal nodes should be appropriately labelled and referenced in one of the following ways. Internal nodes need not be.
[ ] A meaningful external identifier (a combination of database or resource and identifier/accession within that database).
We generate with taxize, #24
[ ] For specimens, museum, collection (if applicable), and specimen identifier. Alternatively, if a specimen is not in a museum collection, use the laboratory, laboratory collection, and accession within that collection.
[ ] Precise (GPS) georeferences for specimens are highly desirable (but not always available).
[ ] Branch lengths: Some measure of branch length required unless it is not applicable to the analysis method.. Further semantics of the measure should be implied by the tree inference method. length attribute in nexml is sufficient
[ ] Branch support: Some value of branch support should be provided, for example posterior probability, or bootstrap value, unless it is not applicable to the analysis method. meta annotation of edge node. example?
Character matrix:
I note that this description is entirely in reference to the character matrix being data from which the tree was derived. It appears that the MIAPA standard doesn't refer to comparative trait data. Further, it many not always be desirable to include a copy of the character matrix in the data file, where that alignment can be found in a separate file might suffice?
[ ] aligned data matrix that is the basis for the tree (by having been the input for the tree inference method)
MIAPA shows an example how how to state that the tree wasDerivedFrom the alignment, not sure whe corresponding rdfa in the nexml would look like
[ ] Data type must be provided, for example DNA, RNA, protein, morphology, etc.
For molecular matrices, the accession numbers (and respective database(s) if different from Genbank) of the sequences used for each row must be provided.
[ ] a mapping that relates each row identifier to a tip of the topology otu attribute present on row
[ ] a mapping that relates each accession number or specimen identifier to a row label inverse of the above map
Alignment method
[ ] name of software used, version of program
MIAPA defines that the alignment wasGeneratedBy some software.
[ ] parameters used (or default if default values were used).
[ ] whether alignment was manually corrected or edited
Character trait data
This is not part of the draft MIAPA standard, but merely my own suggestions/brainstorm list, based on the required metadata for EML description of character traits
[ ] character trait name (Or trait label/definition pair)
[ ] possible states a discrete trait can have
[ ] units (for continuous traits)
[ ] methodological description of how the trait was measured
cboettig
commented
10 years ago
RNeXML should optionally be able to include all the basic metadata listed on the MIAPA checklist, hopefully guiding users that are unfamiliar with the process and being able to provide reasonable automated suggestions when possible (e.g. suggesting external identifiers based on OTU labels, #24) A function might be provided that could check (and perhaps summarize/return) miapa compliance(?).
I've reproduced the checklist below with notes added on how we're doing in RNeXML.
For each item, I've either made a note on if/how we handle it in NeXML, or a question when I'm unsure how to handle it. For instance, I can sometimes find a corresponding block in the example files in the miapa repo, but they are in OWL and the translation to NeXML's meta/RDFa isn't clear to me. An example nexml file that satisfies all these requirements would be super helpful to me.
Topology
treenode<tree>or<network>root="true"on a member nod__. Should we consider declaring this in metadata too?[ ] The type of consensus if this a consensus topology (that summarizes the topology inference in some way, rather than being directly provided by the inference method)
Do we use the treebase namespace for this as well? e.g.
OTUs:
All terminal nodes should be appropriately labelled and referenced in one of the following ways. Internal nodes need not be.
Character matrix:
I note that this description is entirely in reference to the character matrix being data from which the tree was derived. It appears that the MIAPA standard doesn't refer to comparative trait data. Further, it many not always be desirable to include a copy of the character matrix in the data file, where that alignment can be found in a separate file might suffice?
MIAPA shows an example how how to state that the tree
wasDerivedFromthe alignment, not sure whe corresponding rdfa in the nexml would look likeAlignment method
MIAPA defines that the alignment
wasGeneratedBysome software.Character trait data
This is not part of the draft MIAPA standard, but merely my own suggestions/brainstorm list, based on the required metadata for EML description of character traits
Tree inference method