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="Relbutton_Scenarios" />
  </query-continue>
  <query>
    <pages>
      <page pageid="1603" ns="0" title="Read Log">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">A Read Log is like a [[Listen Log]], but for readers of digital text.</rev>
        </revisions>
      </page>
      <page pageid="1392" ns="0" title="Related efforts">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">
== boilerplate text that hardware customers could start sticking into purchase orders ==

[http://zgp.org/pipermail/linux-elitists/2006-December/011756.html From Don Marti on the ] [http://zgp.org/pipermail/linux-elitists linux elitists list]:

''begin Rick Moen quotation of Thu, Dec 14, 2006 at 03:01:59PM -0800:

'''''To very slightly misquote Douglas Adams, &quot;To summarize the summary of a summary: mulish hardware companies are a problem.&quot;'''''

''Some if it is just plain corporate inertia -- sometimes it's easier for Management to put a developer to work trying to play catchup maintaining a proprietary driver than to come up with a GPL release policy.

''In the early days of LCD panels, some vendors redefined a &quot;good&quot; panel as one with fewer than n bad pixels.  Buyers defended themselves with &quot;no bad pixels&quot; terms in purchase orders.''

''A vendor sales person with a signed purchase order from you is a powerful tool for shaping vendor policy your way.  You're talking someone who knows how to persuade, who knows who the players at the company are, who has an incentive to make things come out your way.''

''I'm thinking about drafting some boilerplate text that hardware customers could start sticking into purchase orders.''

Using purchase orders to make purchases could be a useful VRM tool.  When you use a business credit card to buy something, the only side that has a chance to throw legal requirements into the deal is the vendor side.  Use a purchase order and your company's terms apply.

Two other posters on the same thread mention one organization and some other companies that are already using the PO to ensure that the vendor won't slip  software with a one-sided license into a deal.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>