You are looking at the HTML representation of the XML 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 XML format, set format=xml.
See the complete documentation, or API help for more information.
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapcontinue="Reading3S22" />
  </query-continue>
  <query>
    <pages>
      <page pageid="3281" ns="0" title="Reading1S22">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">=Reading 1: Autostereograms (April 19)=

This week's reading is going to be the [https://en.wikipedia.org/wiki/Autostereogram Wikipedia article on autostereograms].

You don't need to read the entire article, but there's one thing I'd like you to do before the lecture on April 19: try to see the second to the last image on that web page, the chess board, in 3D. Click on it to make it larger. Play around with different distances at which you view it to see what works best for you.

If you have more time, see how many of the other stereograms on the Wikipedia page you can see in 3D.</rev>
        </revisions>
      </page>
      <page pageid="3286" ns="0" title="Reading2S22">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">=Volumetric Displays=

This week's reading is on volumetric displays. They can provide an alternative to head-tracked 3D displays because they support multiple viewers at the same time, and no headgear is needed. But they also have disadvantages. 

Read this [https://en.wikipedia.org/wiki/Volumetric_display Wikipedia article] and try to find answers to the following question:

&lt;i&gt;What are advantages and disadvantages of volumetric displays compared to typical VR headsets such as the Oculus Quest?&lt;/i&gt;

You don't need to write the answers down, but we'll discuss them in next week's lecture.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>