MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Sambamba",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "86": {
                "pageid": 86,
                "ns": 0,
                "title": "SVN-Developers",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= SVN repository access for developers =\n\nThis page is for open-bio affiliated developers who are making use of SVN based version control systems rather than the traditional CVS based systems. \n\n== Access methods ==\n=== svnserve operates in tunnel mode only ===\nFor security and access control reasons we are not running a daemonized svnserver process or allowing access via HTTP through the Apache mod_DAV/svn module methods. The SVN access method that fits best with our current developer and security model is to run svnserver in \"tunnel\" mode on a per-user basis. This means developers will connect and authenticate via encrypted SSH sessions before svnserver is invoked. In this scenario svnserver is launched in tunnel mode and runs <em>as the user who invoked it</em>.\n\nThe SVN client protocol makes <b>multiple</b> connections to the svnserver binary. Since we only allow access via SSH this means you may be prompted for you developer password <b>several times</b> during some SVN actions, including  <tt>update</tt>, <tt>diff</tt> (over revisions), and <tt>merge</tt>. The easiest way to circumvent having to enter your password multiple times is to set up your ssh-agent process or make use of SSH keypairs for passwordless access via public key encryption. For assistance in setting this up, email the OBF Helpdesk at <em>support at open-bio.org</em>.\n\n=== Public SVN Access ===\n\nPartially implemented at this time, we now have a web based SVN viewer installed:\n\nhttp://code.open-bio.org/svnweb/\n\nMethods for anonymously checking out SVN repositories are still being worked on. It is highly likely, in fact, that when we deploy public SVN access it will be via http://code.open-bio.org.\n\n== Hosted repositories ==\n=== blipkit ===\nBlipkit developer access is achieved only via an SSH tunnel:\n<pre>\nsvn checkout svn+ssh://dev.open-bio.org/home/svn-repositories/blipkit/trunk blipkit\n</pre>\n\n== Additional SVN documentation ==\n\n[http://svnbook.red-bean.com/en/1.1/index.html Version Control with SVN ]"
                    }
                ]
            },
            "296": {
                "pageid": 296,
                "ns": 0,
                "title": "SVNWeb-disabled",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "October 18 2010\n\nWe have temporarily disabled the web interface SVN::Web CGI service while we attempt to determine if it is a participating factor in server availability issues. Regular anonymous SVN client access is unaffected.\n\nPlease contact Chris (dag@sonsorol.org) if this is affecting you and we will attempt to find a reasonable workaround."
                    }
                ]
            }
        }
    }
}