The most basic convention is that fields are grouped into "Sections". These Sections do not necessarily correspond to sections on the form but in many cases they will. For example:
1 <?xml version="1.0" encoding="UTF-8"?>
2 <application-builder-config
xmlns="http://www.curamsoftware.com/schemas/GUMBO/ApplicationBuilderConfig">
3 <pdf-config>
4 <section name="Applicant">
5 <field name="Name" type="append" append-separator=" "/>
6 <field name="SSN"/>
7 <field name="DateofBirth"/>
8 <field name="Gender" type="button-radio"/>
9 <field name="USCitizen" type="button-radio"/>
10 <field name="blackOrAfricanAmerican"
type="button-checkbox"/>
11 <field name="nativeAlaskanOrAmericanIndian"
type="button-checkbox"/>
12 <field name="asian" type="button-checkbox"/>
13 <field name="nativeHawaiianOrPacificIslander"
type="button-checkbox"/>
14 <field name="whiteOrCaucasian"
type="button-checkbox"/>
15 <field name="EthnicOrigin" type="button-radio"/>
16 </section>
17 </pdf-config>
18</application-builder-config>
Sample 14 shows an extract from a PDF Application Builder Configuration. It refers to a section called applicant. Based on Sample 14 line 4, the PDF Application Builder expects the target PDF form to contain a field called "Applicant.Name", a text field. Line 8 refers to a field on the PDF Form called "Applicant.Gender". This field is a radio button, whereas lines 10-14 all refer to fields that are checkbox buttons.