-
While not required, json-ld encourages explicitly declaring a `@type` on all objects.
NeXML relies on declaring an `xsi:type` as a `nex:something` on certain elements, like characters, while mos…
-
This tracks tasks for building on GBIF servers
- [x] Upload mesquite jar to GBIF nexus
- [x] Build nexml using Ant and add the jar to GBIF nexus
- [x] cql-java-1.3.jar to GBIF third party nexus
…
-
such as ^ot:focalClade.
or am I missing something?
-
From Luna on gitter: the example code and pseudocode to get node ages from source trees
https://github.com/OpenTreeOfLife/python-opentree/blob/get-tree/examples/datelife.py
Specifically,
https://…
-
I think that two nodes in tree6754 of study 2918 are mapping to the same otu: otu432184 which is verboten in nexml
-
Need a context file that defines types appropriately, particularly so that any references are typed as `@id` rather than the default `@value`. This way, JSON-LD knows when it sees things like `"otus"…
-
Some files contain a trees element, but no tree definitions.
http://treebase.org/treebase-web/search/downloadAStudy.html?id=10366&format=nexml
other IDs:
S12147 S12523 S12880 S13461
Reported by: mho…
ghost updated
8 years ago
-
@petermr do you also have lookup code for converting accession number -> taxonID for the NeXML / Newick or should I create some? Happy either way just need to know.
-
@mjy talked about maybe a class for ontotrace to make it easier for users to get to certain data, etc.
-
That seems to be the case even if we supply `Accept: application/json` in the request header. The result should be returned in JSON at least optionally.
hlapp updated
8 years ago