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="Research_Agenda_for_the_Banking_and_Finance_Sector" />
  </query-continue>
  <query>
    <pages>
      <page pageid="112" ns="0" title="Regulation/Liability">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">''[[Table of Contents | TOC-&gt;]][[Approaches | Approaches-&gt;]][[Regulation/Liability]]''

{{Filtered_Table||5.1,false}}


''[[Table of Contents | Jump to Table of Contents]]''</rev>
        </revisions>
      </page>
      <page pageid="53" ns="0" title="Report of the Defense Science Board Task Force on Mission Impact of Foreign Influence on DoD Software">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">==Report of the Defense Science Board Task Force on Mission Impact of Foreign Influence on DoD Software==

==Full Citation==

Defense Science Board Task force Department of Defense (2007): Mission Impact of Foreign Influence on DOD Software. U.S. Government. Online Paper.  [http://www.cyber.st.dhs.gov/docs/Defense%20Science%20Board%20Task%20Force%20-%20Report%20on%20Mission%20Impact%20of%20Foreign%20Influence%20on%20DoD%20Software%20(2007).pdf  ''Web'']

[http://cyber.law.harvard.edu/cybersecurity/?title=Special:Bibliography&amp;view=detailed&amp;startkey=DoD:2007&amp;f=wikibiblio.bib BibTeX]


==Categorization==

Overview: [[Government Reports]]

==Key Words== 
Research


==Synopsis==

The Department of Defense faces a difficult quandary in its software purchases in applying intelligent risk management, trading off the attractive economics of COTS and of custom code written off-shore against the risks of encountering malware that could seriously jeopardize future defense missions.  The current systems designs, assurance methodologies, acquisition procedures, and knowledge of adversarial capabilities and intentions are inadequate to the magnitude of the threat.

==Additional Notes and Highlights==</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>