<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>For about 4 months I have been looking for ways of
XML ing the software I was planning to write. My conclusions may be of interest
to others.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>My conclusion as how I should write my application
is:</FONT></DIV>
<DIV><FONT face=Arial size=2>for data definitions I start with a name space file
ie namespace.xml</FONT></DIV>
<DIV><FONT face=Arial size=2>For screen style sheet I may need another namespace
file to help the user choose appearance.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>I then take XSchema, make some additions to it for
input fields, field lengths, field types etc.....</FONT></DIV>
<DIV><FONT face=Arial size=2>and develop a data entry interface that obeys this
"new enhanced Xschema"</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>This was the user can define their own fields and
do a straight forward data entry / edit screen that would look similar to Access
forms.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>I then use XSL definitions to "merge" the data with
the XSL to produce HTML which in the short term I can use Internet explorer for
viewing and printing until I have produced my own viewer.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>For reporting I need XQL which can run down a
nindex file and pull in all items that obeys that index and examine them for the
data in them. This builds an XML data string which then when an XSL style sheet
defn is applied "merges" the data into a HTML document.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>For internet email transmissions there is two
options: sent the HTML file, or send the XML data and XSL style sheet
definitions so the package at the other end can produce the HTML
view.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>The implications of this approach are:</FONT></DIV>
<DIV><FONT face=Arial size=2>Must constrain all functions to produce acceptable
HTML</FONT></DIV>
<DIV><FONT face=Arial size=2>do not need XFA, XFDL, or any other not yet
recommended standard.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Have to produce an XSchema of my own, but since it
is only used in my package it does not matter if it does not conform to any
standards.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></BODY></HTML>