Allows form designers to add application specific information
to the form definition.
This is useful when submitting forms to
applications requiring non-XFDL information. An example of non-XFDL
information might be a SQL query statement.
Available options
All
XFDL options, the xforms:input or xforms:textarea options,
and any custom options can be used with custom items.
Example
This
is an example of a custom item definition. It includes both an XFDL
and a custom option.
<custom:event xfdl:sid="STATUS_EVENT"
xmlns:custom="http://www.ibm.com/xmlns/prod/XFDL/Custom">
<xfdl:active>off</xfdl:active>
<custom:ID>UF45567/home/users/preferences01</custom:ID>
</custom:event>
Usage details
- Custom
items must be in a non-XFDL namespace.
- Custom items can also change the default namespace
from the XFDL namespace URI in order to eliminate excess prefixes
within the desired namespace.
- Custom items may omit the XFDL scope identifier,
but a sid attribute in the XFDL namespace must
be provided in order to reference the custom item's content with the
XFDL compute system. Since default namespaces are not applied to attributes,
the sid attribute must still be qualified by a
namespace prefix associated with the XFDL namespace URI.
- Both XFDL options and custom options within the
custom item can have computed values by using the XFDL compute attribute,
which must be qualified with a namespace prefix associated with the
XFDL namespace URI.