1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 2 <html xmlns="http://www.w3.org/1999/xhtml"> 3 <head> 4 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" /> 5 <title>Creating Applications: Design the Structure of the Form Data</title> 6 <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" /> 7 <link href="styles.css" rel="stylesheet" type="text/css" /> 8 </head> 9 <body> 10 11 <h1>Creating Applications: Design the Structure of the Form Data</h1> 12 13 <p>Before designing a template, we must first consider how the form 14 data to be modelled in our application will be structured. Let us 15 consider the following hierarchical structure:</p> 16 17 <ul> 18 <li>A list of items, each containing...<br /> 19 <ul> 20 <li>An editable value.</li> 21 <li>A list of subitems, each containing...<br /> 22 <ul> 23 <li>An editable value.</li> 24 </ul> 25 </li> 26 </ul> 27 </li> 28 </ul> 29 30 <p>Since XSLForms is an XML-based framework, let us define this structure using an informal example XML document:</p> 31 <pre><?xml version="1.0"?><br /><structure><br /> <item value="some value"><br /> <subitem subvalue="some other value"/><br /> </item><br /></structure></pre> 32 <p>The above example only shows a single item and a single subitem 33 within it. Our application will provide the ability to add and remove 34 items and subitems, although this is not directly modelled in the XML 35 documents that will be used to represent the form data.</p> 36 <p>With this basic information defined, we can now proceed to <a href="design.html">designing a template</a> in the next stage of the <a href="overview.html">process</a>.</p> 37 38 </body> 39 </html>
