<?xml version="1.0"?>  <!-- notice contentType -->
<?xml-stylesheet type="text/xsl" href="http://neolectric.com/dxp/samplexml/basic.xsl" ?>
<doc>
 <title>dxp: XML samples</title>
 <section>
  <pg>
  You can use dxp to generate dynamic xml documents. First you need to tell the browser that your
  dxp page will deliver xml, not html<br /><br />
  &lt;dxp:DxpPage xmlns:dxp="dxp.neolectric.com" <b>contentType="text/xml"</b>&gt;
  </pg>
  <pg>
  If you want the browser to format the xml into html using an xsl stylsheet you have to include a
  referenc to the stylesheet. For a <b>static xml</b> page you can do it this way (a basic example)<br /><br />
  &lt;?xml-stylesheet type="text/xsl" href="http://neolectric.com/dxp/samplexml/basic.xsl" ?&gt;<br />
  </pg>
  <pg>
  If you use dxp to genterate <b>dymamic xml</b> you have to tell the page parser to leave
  the stylesheet tag alone. The CDATA tag will do that.<br />
  <b>&lt;![CDATA[</b> &lt;?xml-stylesheet type="text/xsl" href="http://neolectric.com/dxp/samplexml/basic.xsl" ?&gt; <b>]]&gt;</b><br />
  </pg>
 </section>
 <section>
  <title>Samples</title>
  <pg>My browser (Mozilla) experiences a brief delay while it renders xml into html.</pg>
  <pg><url href="xrecordset.xml">dxp to xml - basic stylesheet</url></pg>
  <pg><url href="loop-nested-xml2.dxp">write xml file from db results</url></pg>
  <pg>Raw xml below (no stylesheet) you will have to "View Page Source" to see the xml tags</pg>
  <pg><url href="loop-nested-xml.dxp">raw xml from db returned with - no stylesheet</url></pg>
  <pg><url href="basic.xsl">Basic xsl stylesheet</url></pg>
 </section>
 <section>
 <title>Footnote</title>
  <pg>
  Old browsers don't support xml and that's often cited as the reason to continue producing web apps
  that only deliver html. In many cases the real reason may a reluctance to invest time and energy
  to learn a new medium as long as you can get by with something familiar.
  </pg>
  <pg>
  My experience with xsl stylesheets is limited and there are things about the model that annoy me.
  On the other hand, it's handy to keep all your rendering code in one place rather than inserting
  it into all your data pages. It's certainly useful for rendering your own custom tags.
  </pg>
 </section>
</doc>

