MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": [
            {
                "ns": 0,
                "title": "API",
                "missing": ""
            },
            {
                "pageid": 1,
                "ns": 0,
                "title": "Main Page",
                "revisions": [
                    {
                        "user": "WikiSysop",
                        "timestamp": "2016-04-13T15:47:38Z",
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "comment": "Reverted edits by [[Special:Contributions/MediaWiki default|MediaWiki default]] ([[User talk:MediaWiki default|talk]]) to last revision by [[User:Hilmar|Hilmar]]",
                        "*": "== Who we are ==\n\nThe EvoIO collaboration emerged in 2009 from several NESCent-sponsored activities that focused on software and data interoperability for evolutionary analysis, including the Evolutionary Informatics working group (2006-2009), and the Evolutionary Database Interoperability hackathon (2009).  EvoIO aims to be a nucleating center for developing, applying and  disseminating interoperability technology that connects and coordinates between stakeholders, developers, and standards bodies. \n\nMembers of the EvoIO group, which include biologists and computer scientists, have over the past 3  years harnessed a variety of collaborative events to successfully build an initial stack of interoperability  technologies that is owned by the community and open to participation: \n* [http://nexml.org NeXML], a NEXUS-inspired XML format that is validatable yet extensible\n* [http://www.evolutionaryontology.org CDAO], an ontology of comparative data analysis formalizing the semantics of evolutionary data and metadata; and \n* [http://evoinfo.nescent.org/PhyloWS PhyloWS], a web-services interface standard for querying, retrieving, and referencing phylogenetic data on the web. \n\nFor more information about how to get involved, read on.  \n\n== What's happening ==\n* A grant proposal to NSF's Advances in Biological Informatics (ABI) program titled \"An Ontology-Based System for Querying Life in a Post-Taxonomic Age\" (PIs: Cellinese and Lapp) has now been funded. The proposal and public abstract are available on Figshare ([http://dx.doi.org/10.6084/m9.figshare.1401984 doi:10.6084/m9.figshare.1401984]). The project picks up some ideas from the [[Phyloreferencing subgroup]] of the [[VoCamp1|Phyloinformatics VoCamp]]. \n\n* Many of us are PIs or Leadership Team members of a NESCent working group called [http://www.evoio.org/wiki/HIP Hackathons, Interoperability, Phylogenies (HIP)].   HIP is the current locus of most of our activity .  So far we have had two '''[[Phylotastic]]''' hackathons focused on a web-services implementation of the pruning, grafting, name-reconciliation and other functionalities necessary for researchers to take advantage of emerging megatrees.  HIP is planning a third hackathon to develop a socially networked phyloinformatics community of practice.  \n\n* We organized a workshop on \"[http://docs.google.com/document/pub?id=1DiuMEK7g_DJSLzT9ElAwEtJiKRXuQAvoc0JtfoX0sqE Steps towards a Minimum Information About a Phylogenetic Analysis (MIAPA) Standard]\" at the 2011 TDWG Conference in New Orleans, LS. The workshop took place on Monday, Oct 17, and Tuesday, Oct 18. The goal of the workshop was to determine how a future reporting standard for phylogenetic analyses can best serve biodiversity science and related research applications. \n\n* We submitted an [[ABI 2011 proposal|NSF ABI proposal]] on development and (finally!) linking TreeBASE and ToLWeb, entitled \"Towards a comprehensive, community- owned and sustainable repository of reusable phylogenetic knowledge\" (Lapp, Bietz, Cranston, Piel, Donoghue, Westneat). The proposal was not funded.\n\n* At [http://ievobio.org/ iEvoBio] 2011 in Norman, OK, Arlin Stoltzfus gave a talk on \"Publishing re-usable phylogenetic trees, in theory and practice\"\n\n* In December 2010, EvoIO participants submitted a proposal to NESCent for a working group entitled [[HIP| HIP: Hackathons, Interoperability, Phylogenies]] (Vos, Stoltzfus).  The proposal is for a series of hackathons partly supported by outside partners.  NESCent recently announced that this proposal will be funded.  Woo hoo!\n\n* A proposal for a new NESCent course titled \"Phyloinformatics: linking with online data and services\" was submitted by EvoIO participants (Stoltzfus, Vos, Cranston, Lapp) in July 2010 and subsequently selected for funding, but had since to be canceled due to conflicting obligations of the PIs. Instead, Vos and Piel co-taught a [http://academy.nescent.org/wiki/Computational_phyloinformatics Computational Phyloinformatics course] modeled after previous instances of this course, but supplemented with programming exercises using PhyloWS wrappers for ToLWeb and uBio. The course was held in Kyoto in August 2011, and supported by the Bioinformatics Center of Kyoto University and DBCLS/JST, with co-sponsorship by NESCent.\n\n* EvoIO participants in various ways participated in the [http://ievobio.org iEvoBio satellite conference] at Evolution 2010 in Portland, OR:\n** Rutger Vos gave a talk on \"TreeBase2: Rise of the machines\" (Rutger Vos, Hilmar Lapp, Bill Piel, Val Tannen)\n** Brandon Chisham presented \"CDAO-Store: A New Vision for Data Integration\" (Brandon Chisham, Trung Le, Enrico Pontelli, Tran Son, Ben Wright)\n** Arlin Stoltzfus presented \"EvoIO: Community-driven standards for sustainable interoperability\" (Arlin Stoltzfus, Nico Cellinese, Karen Cranston, Hilmar Lapp, Sheldon McKay, Enrico Pontelli, Rutger Vos)\n\n* The EvoIO group staged a successful [[VoCamp1|Phyloinformatics VoCamp]] November 7-11, 2009 in Montpellier, France, co-located with the annual meeting of the <span class=\"plainlinks\">[http://www.tdwg.org/ International Biodiversity Information Standards Organization (TDWG)]</span>.   A VoCamp is a hands-on meeting for investigators to create and develop ontologies and lightweight vocabularies in support of data integration and re-use-- in this case, the integration and re-use of phylogenetic trees and associated data and metadata.  More information at [[VoCamp1]].\n\n* We submitted a proposal to the NSF INTEROP panel in 2009 for \"A network for enabling community-driven standards to link evolution to the global web of data (EvoIO)\". More information at [[NSF INTEROP 2009|NSF INTEROP 2009]]. This proposal was not funded.\n\n== How to get involved ==\n\nHow to get involved?  Each stack component has an open community of developers and a mailing list.  Click on the links below to find out more.  You can sign up for the mailing list and start to contribute.  \n* [http://nexml.org NeXML]'s mailing list is nexml-discuss@lists.sourceforge.net (contact Rutger Vos, <firstname>aldo@gmail.com)\n* [http://evoinfo.nescent.org/PhyloWS PhyloWS]'s group is phylows@googlegroups.com (contact Hilmar Lapp, <firstinitial>lapp@nescent.org) \n* [http://www.evolutionaryontology.org CDAO]'s mailing list is cdao-discuss@lists.sourceforge.net (contact Arlin Stoltzfus, <firstname>@umd.edu)\n* [http://pipes.yahoo.com/pipes/pipe.run?_id=b269b02171b6411c4a27ae0714dc76da&_render=rss RSS feed of relevant projects]\nAlso EvoIO folks are looking for interoperability \u201ctargets\u201d, which can be either single projects that want to make resources more interoperable, or pairs of resources that want to integrate.  Contact any of us if you have an idea.\n\n== MediaWiki Help if you need it ==\n\n* [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide]\n* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]"
                    }
                ]
            }
        ]
    }
}