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": "",
    "continue": {
        "gapcontinue": "Real-time",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "8383": {
                "pageid": 8383,
                "ns": 0,
                "title": "ReGIS",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''ReGIS''' (the more common, acronym, form of the full name, '''Remote Graphics Instruction Set''') was a descriptive language (effectively, an [[application]] [[protocol]] in today's terminology) created by [[Digital Equipment Corporation|DEC]] for sending [[graphics]] content to a remote [[graphics terminal]] (a [[workstation]] in the original implementation, the [[VK100]] GIGI).\n\n{{semi-stub}}\n\n==External links==\n\n* [http://bitsavers.org/pdf/dec/terminal/gigi/TR-95_Fundamentals_Of_ReGIS_Jul79.pdf Fundamentals of the Remote Graphics Instruction Set (ReGIS)] (DEC/TR-95)\n* [http://bitsavers.org/pdf/dec/terminal/gigi/AA-K336A-TK_GIGI_ReGIS_Handbook_Jun81.pdf GIGI/ReGIS Handbook] (AA-K336A-TK)\n\n[[Category: DEC Graphics Terminals]]\n[[Category: DEC Standards]]"
                    }
                ]
            },
            "474": {
                "pageid": 474,
                "ns": 0,
                "title": "Read-only memory",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''ROM''' is simply '''Read Only Memory'''.\n\nUnlike [[Random Access Memory|RAM]], ROMs cannot be written to. At one point, ROMs are also typically slower than RAM.\n\nROMs come in several flavors:\n\n== PROM ==\n\nPROMs can be programmed ONCE then read many times.  If there are any mistakes in the PROM code, the entire chip must be discarded.  While PROMs can be read in a normal board, they need to be programmed in a special device (since programming them often requires special [[voltage]]s).\n\n== EPROM ==\n\n[[Image:M27C512 EPROM.jpg|150px|right|An EPROM]]\n\nEPROMs can be erased after they have been programmed.  Normally there is a small window in the chip in which exposure to UV light will erase the EPROMs programming.  EPROMs also need to be programmed in a special programmer.\n\n== EEPROM ==\n\nEEPROMS can be erased electronically, and re-programmed, usually through the application of higher than normal voltage. In modern EEPROMS this is generated internally. Unlike EPROMs, EEPROMS can be re-written in-circuit.\n\n==External links==\n\n* [http://madrona.ca/e/corerope/index.html Core Rope & Woven-Wire Memory Systems]\n\n[[Category: Computer Basics]]"
                    }
                ]
            }
        }
    }
}