The logical connection between a form control and a component of the data source of an InfoPath form. If a form control is not bound to part of the data source, any data entered into the form control is not saved or submitted from the form.
data source
The XML data structure that forms the basis of the data collected by or returned to an InfoPath form. The data source, which consists of XML elements and attributes, is exposed in the InfoPath user interface as groups and fields . The XML data source can be derived from a relational database such as Access or SQL Server, or from an XML Web service.
data validation
See [validation]
element
An XML structure that can be exposed in the InfoPath data source as either a group (if it has element content) or a field (if it has no element content).
field
A component of the data source of an InfoPath form that can't have any descendant components . An InfoPath field corresponds to an XML element with no element content or to an XML attribute.
form
An XML file associated with a form template. The association is specified in a processing instruction.
form area
The main screen area that is situated to the left of the task pane by default.
form definition file
The .xsf file, which is an XML file containing information about all the other files that make up a form template . Also called a manifest .
form files
A collective term for the files that underlie an InfoPath form template. The form files can exist as individual files in a single directory or can be aggregated in the form template .
form template
A file with an .xsn file extension. A cabinet file containing the form files , including the form definition file (the .xsf file), XSLT files to create views, W3C XML Schema files, and so on.
fully trusted form
A form that is explicitly installed on a user's machine and therefore allows the use of security level 3 components of the InfoPath object model. Fully trusted forms are allowed unrestricted access to system resources. Also called a URN-based form, because a URN must be specified in the name attribute of the xsf:xDocumentClass element of the form definition file .
group
A component of the data source of an InfoPath form that has further groups or fields or both as descendants.
manifest
An alternate term for the form definition file , because the form definition file is named manifest.xsf by default.
Microsoft Script Editor
The integrated development environment in which JScript and VBScript code for an InfoPath form template can be created and edited.
RegForm
A utility supplied in the InfoPath SDK that allows fully trusted forms to be installed on a user's machine.
repeating section
An InfoPath form control that is bound to a group in the form's data source .
repeating table
An InfoPath form control with a tabular layout that's bound to a group in the form's data source .
sandboxed form
An InfoPath form template that has been published to a Windows SharePoint Services form library, to a standard Web site, or to a Windows file share. Sandboxed forms have limited access to system resources. Sandboxed files are also called URL-based forms .
security level
A property of InfoPath object model properties and methods that specifies the security situation in which those properties and methods are permitted to be used. InfoPath 2003 defines security levels 0, 2, and 3.
solution file
A term sometimes used to refer to the .xsn form template file.
template file
An XML file, also called the XML template file, in the form template file that contains a sample XML document demonstrating the allowed structure of the XML data.
URL-based form
Synonym of sandboxed form .
URN-based form
Synonym of fully trusted form .
validation
A process of determining whether a data value corresponds to constraints on allowable values.
view
A view of part or all the form data. Views are created by XSLT files, which are contained in the form template.
W3C XML Schema
A language, used in InfoPath validation , which expresses constraints on the allowable values of a piece of data.
