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>
    <search sroffset="10" />
  </query-continue>
  <query>
    <search>
      <p ns="0" title="Technical Team/Minutes/2011-03-29" snippet="** We discussed the name and &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of the “NonStandardLicense”. Agreed to rename the field (see spreadshee&#10;" size="2929" wordcount="419" timestamp="2013-03-06T13:56:23Z" />
      <p ns="0" title="Technical Team/Minutes/2011-04-26" snippet="* Discussed &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of the terms.&#10;" size="2548" wordcount="376" timestamp="2013-03-06T13:06:46Z" />
      <p ns="0" title="General Meeting/License Field Discussion" snippet="...n multiple discussions in different working groups about the nomenclature, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; and intent of the package license fields. To ensure we are all on the right&#10;" size="2056" wordcount="328" timestamp="2013-03-06T11:28:39Z" />
      <p ns="0" title="Legal Team/Minutes/2011-08-10" snippet="* Discussion about &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of compliance with CC license: current license only requires attribution (b&#10;" size="7156" wordcount="1125" timestamp="2013-03-05T18:45:37Z" />
      <p ns="0" title="Legal Team/Minutes/2012-04-05 (LF Collab Summit)" snippet="...license name and identifier) for each header scenario that can change the &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of the license (e.g. GPL-2.0; GPL-2.0+)&#10;" size="4489" wordcount="732" timestamp="2013-03-05T18:52:24Z" />
      <p ns="0" title="General Meeting/Minutes/2013-04-CollabSummit" snippet="...hey would like to see SPDX become more fully integrated into the community &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that practices normally associated with an open source project such as peer&#10;" size="5733" wordcount="970" timestamp="2013-04-27T11:44:41Z" />
      <p ns="0" title="Legal Team/Minutes/2013-04-25" snippet="...disagreement there is even amongst people close to the license in terms of &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; and interpretation&#10;" size="4932" wordcount="781" timestamp="2013-04-25T18:04:11Z" />
      <p ns="0" title="Legal Team/License List/Licenses Under Consideration" snippet="| issue of potential confusion with short identifier &amp;quot;GPL-2.0&amp;quot; &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; GPLv2 only; whereas GPLv2 or later, uses short identifier &amp;quot;GPL-2.0+&amp;quot; should&#10;" size="12935" wordcount="1920" timestamp="2017-09-16T17:11:49Z" />
      <p ns="0" title="Legal Team/Minutes/2013-11-07" snippet="...at once. these licenses will be identified as &amp;quot;queued&amp;quot; in the Google doc - &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; we have no major objectino to add them, but they just seem so rare it is no&#10;" size="4192" wordcount="731" timestamp="2013-11-07T19:12:37Z" />
      <p ns="0" title="Technical Team/Minutes/2016-02-09" snippet="** Proposed: optional sections have &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; ONLY in the context of matching licenses. They specify sections of text tha&#10;* Decide on / confirm the semantic &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of optional sections of the markup.&#10;" size="6391" wordcount="1021" timestamp="2016-02-18T05:18:19Z" />
    </search>
  </query>
</api>