You are looking at the HTML representation of the XML format.
HTML is good for debugging, but probably is not suitable for your application.
See complete documentation, or API help for more information.
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapfrom="Reproducibility and Reliability Working Group" />
  </query-continue>
  <query>
    <pages>
      <page pageid="297" ns="0" title="Reliability">
        <revisions>
          <rev xml:space="preserve">=== Notes from Breakouts ===

The comments from breakout groups discussing reliability and reproducibility are provided below:

* [[Group1 | Group A]]
* [[Group2 | Group B]]
* [[Group3 | Group C]]
* [[Group4 | Group D]]

The previous work from the Working group has been documented on the wiki at http://www.cansas.org/wgwiki/index.php/Reproducibility_and_Reliability_Working_Group

Past messages for the mail group are available at:
https://groups.google.com/forum/#!forum/cansas-rrwg and there is a button marked 'Apply to join group'.

=== Summary from Plenary ===
During the wrap up the primary topic that came up in many different ways from several groups was the idea of developing new standards in some way and doing round-robins on those.  Some discussion of how to achieve that was had during the short plenary wrap up in fact.  Other topics that came to the plenary included including multiple scattering warnings and modeling into data reduction and analysis software and documenting good practices in data reduction.  finally, two topics brought up from the individual breakouts: multi mode methods and analysis; and database/repository of careful measurements with appropriate metadata were deemed to be topics that we be presented and discussed in day 2: data analysis.  

=== Agreed actions from the meeting on 5 June 2017 include: ===

*Prepare some new potential Q, I, and resolution standard materials, covering a broad range of measurements including soft X-rays and GI techniques. Then use in round-robin to test utility. 
** A group at NIST (Joe Kline, Ron Jones, Paul Butler) will meet to discuss what type of samples (focusing probably on 'grating-type') could be prepared.  Nick Terril from Diamond will participate by telecon.
** Chris Tassone will send out an email to the list of participants asking for willing to participate in measurements of new round-robin samples.
* Work to include multiple scattering in reduction and analysis codes
** Working group volunteers: Grethe Jensen, Tim Snow, Brian Pauw, Javier Perez, Tom Caswell?
* Prepare a guide on best practices in data reduction for a few standard classes of experiments.
** Brian Pauw leading: a number of people wanted to join will email Brian their interest so he can capture the names.</rev>
        </revisions>
      </page>
      <page pageid="155" ns="0" title="Rendering canSAS1D in Web Browsers">
        <revisions>
          <rev xml:space="preserve">
== Using a stylesheet with CanSAS XML files ==

One of the benefits of XML is that with an appropriate stylesheet, web browsers should be able to render the page as HTML, and other XML-compliant applications can interpret what a file contains and do something sensible with it.

In order to use this feature, the XML file must have a stylesheet associated with it. This can either be local to the machine the XML file resides on, or accessed via a remote URL.

A default stylesheet is provided for the cansSAS1D format at: [http://www.smallangles.net/cansas1d/1.0/cansasxml-html.xsl http://www.smallangles.net/cansas1d/1.0/cansasxml-html.xsl]

In order to use this, there must be a line in the XML data file (usually the second line, after the xml declaration itself) as follows:

 &lt;?xml-stylesheet type=&quot;text/xsl&quot; href=&quot;http://www.smallangles.net/cansas1d/1.0/cansasxml-html.xsl&quot;?&gt;

Thus the header will look something like:

 &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
 &lt;?xml-stylesheet type=&quot;text/xsl&quot; href=&quot;http://www.smallangles.net/cansas1d/1.0/cansasxml-html.xsl&quot;?&gt;
 &lt;SASroot version=&quot;1.0&quot; 
    xmlns=&quot;cansas1d/1.0&quot; 
    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; 
    xsi:schemaLocation=&quot;cansas1d/1.0  http://www.smallangles.net/cansas1d/1.0/cansas1d.xsd&quot;&gt;
 &lt;SASentry&gt; ...

== Browser Compatibility ==

However, having a local file referencing a remote one is sometimes considered to be a security risk by certain browsers. Thus in some cases it may be necessary to store the XSL file locally and change the URL in the header appropriately.

Below is a list of various browsers/OS combinations and how they behave. The list is not comprehensive.

=== Windows 7 ===

* IE 8
** Works with local and remote stylesheets
* IE 9
** Works with local stylesheets only after altering the browser security settings (Internet Options-&gt;Security-&gt;Custom Level, and then under &quot;Miscellaneous&quot; enable &quot;Access data sources across domains&quot;)
* Firefox 10
** Works with local stylesheets only
* Google Chrome
** Does not work with remote or local stylesheets
* Opera
** Not tested
* Safari
** Not tested

=== Mac OS ===

* Safari 5
** Works with remote and local stylesheets with no changes
* Google Chrome
** Does not work with remote or local stylesheets
* Firefox 6
** Works with local stylesheets only
* Opera
** Not tested

=== Linux ===
* Firefox
** Not tested but assume the same behaviour as other platforms

=== iOS ===
* Mobile Safari
** Not tested
* Opera Mobile/Mini
** Not tested

=== Android ===
* Dolphin &amp; Dolphin HD
** Not tested
* Firefox
** Not tested but assume the same behaviour as other platforms
* Opera Mobile/Mini
** Not tested</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>