Search results

Jump to: navigation, search

Page title matches

Page text matches

  • * [http://nexml.org NeXML], a NEXUS-inspired XML format that is validatable yet extensible * [http://nexml.org NeXML]'s mailing list is nexml-discuss@lists.sourceforge.net (contact Rutger Vos, <firstname>aldo@gmail.co
    7 KB (975 words) - 10:47, 13 April 2016
  • ...protocol for the maintenance and extension of our standards (e.g. CDAO and NeXML). This pitch is more about social engineering than software engineering: ho ...t existing files don't break in the updated schema - we've seen this with NeXML. I think the pitch group would be most useful if it focussed on schema mai
    22 KB (3,521 words) - 06:11, 13 November 2009
  • ...The EvoInfo working group, which was active from 2006 to 2009, spawned the NeXML, CDAO and PhyloWS projects, and helped to organize 2 hackathons. [[Category:NeXML]]
    5 KB (637 words) - 10:34, 27 April 2011
  • * [http://www.nexml.org/ NeXML], an exchange standard for representing phylogenetic data — inspired by t
    8 KB (1,057 words) - 06:10, 13 November 2009
  • ...voinfo.nescent.org/ NESCent EvoInfo Working Group], [http://www.nexml.org/ NeXML], [http://treebase.org TreeBase]
    7 KB (979 words) - 15:26, 15 November 2009
  • ...a (social) relation with, e.g. ZFin. Q: How does making data available as NeXML help others reuse the data? Tangible outcomes? * RV: treebase, metadata, nexml, phyloWS
    8 KB (1,120 words) - 13:00, 9 December 2009
  • ...instances: 1. character state matrix from phenoscape KB, 2. build a dummy NexML tree and convert to CDAO RDF. ...nd character matrix [https://nexml.svn.sourceforge.net/svnroot/nexml/trunk/nexml/examples/translations/tdwg09.rdf character state and tree input file]
    10 KB (1,531 words) - 11:16, 11 November 2009
  • ...semantically rich metadata (<span class="plainlinks">[http://www.nexml.org NeXML]</span>), a standard programmable interface to online phylogenetic data res ...orts to adopt some of the standards, for example incorporating PhyloWS and NeXML-support into the next-generation version of the community resource TreeBASE
    12 KB (1,666 words) - 06:17, 13 November 2009
  • ** NeXML ms is nearing completion
    4 KB (526 words) - 13:45, 7 November 2010
  • ...x for solving interoperability problems, based on the EvoIO “stack” of NeXML, CDAO and PhyloWS. This toolbox makes it possible to begin building a world ...etadata (Vos, et al., in review.; http://www.nexml.org). Data expressed in NeXML can be annotated with terms from the CDAO and other knowledge representatio
    28 KB (4,144 words) - 13:54, 19 January 2012
  • ...ect "[http://informatics.nescent.org/wiki/PhyloSoC:_NeXML_to_MIAPA_mapping NeXML to MIAPA mapping]"
    3 KB (425 words) - 17:14, 1 June 2018
  • *** project lists (nexml-discuss@sf, cdao-discuss@sf, phylows@googlegroups.com
    21 KB (3,131 words) - 09:06, 1 August 2011
  • Build a tool that will allow users to create a NeXML file with minimal information to document a phylogenetic analysis. # work out NeXML representation of methods concepts using CDAO terms (also OBI?)
    10 KB (1,397 words) - 11:02, 19 August 2011
  • ...either concrete (a newick tree) or a pointer (to a treebase accession or a nexml object)
    8 KB (1,095 words) - 20:20, 17 October 2011
  • ...procedures to explicitly relate tree descriptions to data matrices within NeXML files. We view this as an important step in the development and specificat
    7 KB (1,010 words) - 15:33, 1 June 2011
  • ...onic form that can be processed without loss of information (e.g., Newick, NeXML; graphics files are not sufficient).
    4 KB (571 words) - 17:40, 28 October 2011
  • * our past success in developing interop technologies nexml, CDAO and PhyloWS * the 3-part interop formula of data syntax (nexml), semantics (CDAO) and services (phyloWS)
    6 KB (897 words) - 12:34, 15 July 2011
  • Hackathon 1: issue is integrating API and data formats. We could use NeXML as the format. The hackathon could also indicate what is missing in the sta Maybe we should validate NeXML implementations instead. Ensure that all the implementations are correct an
    64 KB (9,637 words) - 11:10, 8 April 2013
  • === NeXML -> R converter === === NeXML round-tripping ===
    32 KB (5,051 words) - 08:01, 15 May 2013
  • * NeXML spec - you can help expand the NeXML spec to cover the Phylotastic use-case
    3 KB (487 words) - 08:17, 20 August 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)