You are looking at the HTML representation of the XML format.
HTML is good for debugging, but probably is not suitable for your application.
See complete documentation, or API help for more information. 
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapfrom="Simple FM transmitter using gnuradio" />
  </query-continue>
  <query>
    <pages>
      <page pageid="239" ns="0" title="SHA 2017 Organisation">
        <revisions>
          <rev xml:space="preserve">==Orga page for SHA2017==
SHA2017 is an international non-profit outdoor hacker camp/conference taking place in The Netherlands in 2017 on August 4th to 8th. [https://wiki.sha2017.org/w/Main_Page The Camp] (for those who don't know what it is) 

Our village: [https://wiki.sha2017.org/w/Village:Opendigitalradio] 

Going: Matthias, Mathias, Rashid, Andreas

Subjects we want to look into, do tests, trials, experiments, whatever:

==Projects==
* Digital Predistortion
* Calculate MER

==Equipment==

Everybody takes power distribution cables!

===Mathias===
*Spectrum analyser?
*?

===Rash===
*?
*NUC ?
*USRP B200
*3.2W PEP Amplifier incl Power Supply

===mpb===
*USRP B200
*LimeSDR
*Directional coupler and attenuators
*RTLSDR
*Some amateur radio stuff
*coloured LED stripes + arduino for decoration
*long ethernet cable

If requested
*USRP B100
*GPSDO modules
*Ethernet router/switch

We have ordered a village tent with tables and chairs, we need some lighting</rev>
        </revisions>
      </page>
      <page pageid="240" ns="0" title="SNMP">
        <revisions>
          <rev xml:space="preserve">Opendigitalradio has reserved a Private Entreprise Number for SNMP: '''51436'''

OID: &lt;code&gt;iso.org.dod.internet.private.enterprise.opendigitalradio&lt;/code&gt; (1.3.6.1.4.1.51436)

The '''goal of the Project SNMP''' is to make the monitoring statistics available through SNMP.

Update January 2022: It is such a pleasure to work with SNMP that this effort has stalled.

==Steps==

; Understand how to represent our monitoring values in a MIB
: List what by whan to monitor and define keyword

; Define a MIB structure and write a MIB
: The best pratice seem to have 1 MIB by product/software and reserve one sub-level for each
: 51436.1 for ODR-DabMux
: 51436.2 for ODR-DabMod
: 51436.3 for ODR-AudioEnc
: 51436.4 for ODR-PadEnc

; As every tool can be run more than once on a machine, all of them need to start with a table.

; Understand how to interface with snmpd and write scripts to connect the mmbTools with snmpd

==Things to monitor==

Things to monitor for the ODR-mmbTools:

* ODR-PadEnc
** Nothing
* ODR-AudioEnc
** Nothing. Audio levels are available through ODR-DabMux
* ODR-DabMux
** Seconds until expiry of TAI bulletin
** For each ZMQ input:
*** state (0 Unknown, 1 NoData, 2 Unstable, 3 Silent, 4 Streaming)
*** min buffer
*** max buffer
*** number of ZMQ underruns (overflows at 2^32 - 1)
*** number of ZMQ overruns (overflows at 2^32 - 1)
*** audio level peak, left channel
*** audio level peak, right channel
** We could add the number of frames encoded, to detect a stuck multiplexer (To be discussed)
* ODR-DabMod
** one set of values for CFR
*** Percentage of samples clipped
*** Percentage of errors clipped
*** MER after CFR
*** PAPR before CFR
*** PAPR after CFR
** The configured TIST offset
** The current TIST value
** To be added: The TIST value of the frame FCT=0
** one set of values for SDR device
*** Number of underruns
*** Number of late packets
*** Number of frames transmitted</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>