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="Splitter" />
  </query-continue>
  <query>
    <pages>
      <page pageid="41" ns="0" title="Scripted">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">A scripted adapter is an [[Atomic adapter|atomic adapter]].

It does not have any particular kind of predetermined behavior: it's up to the script developer to define it through scripting.

In most cases, it'll be probably similar to a [[Filter|''filter'']] or a [[Processor|''processor'']].</rev>
        </revisions>
      </page>
      <page pageid="36" ns="0" title="Selector">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">A selector is a [[Composite Adapter|''composite adapter'']]. 

It manages a group of two or more 'sub-adapters'.

When it receives a granule through its input connection, it will use the [[Granule Acceptance|''granule acceptance'']] mechanism to decide which the most appropriate target adapter is, and it will send the granule to one (and only one) of its sub-adapters.

The output connection of the selector serves as the 'default option': if none of the sub-adapters is prepared to accept a particular granule, then the granule is routed through the output connection of the selector.

[[File:selector.png|800px]]

The sub-adapters are in a sequential list; the position of a sub-adapter in the list is important. 

The sub-adapters are tried out in sequence: the first adapter willing to accept a particular granule will be the one selected. Any subsequent adapters in the selector's sub-adapter list don't even get to 'see' the granule once it's routed to the selected sub-adapter.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>