C
XForms Specification Support

This appendix contains information about XForms specification support. Topics include:

• Section C.1, "XForms Document Structure"

• Section C.2, "XForms Processing Model"

• Section C.3, "DataTypes"

• Section C.4, "Model Item Properties And Schema Constraints"

• Section C.5, "XPath Expression in XForms"

• Section C.6, "XForms UI Controls"

• Section C.7, "XForms Actions"

  Note: OracleAS Wireless also supports a subset of features specified by W3C XForms 1.0 Candidate Recommendation at http://www.w3.org/TR/2002/CR-xforms-20021112/

C.1 XForms Document Structure

Table C-1 XForms Document Structure

XForms Specification	Supported	Comments
XForms Namespace	Yes
Common Attributes	Yes	xsd:ID supported with XHTML as container
Linking Attributes	Partial	Supported only on instance element
Single-Node Binding Attributes	Yes	Not supported in XForms elements label, help, hint, alert or message elements. (Note: The same can be achieved using an <output> control within any of label, help, hint, alert or message element)
Node-Set Binding Attributes	Yes
model Element	Yes	Supports multiple models. Attributes "schema" not supported. Attribute "functions" not supported
instance Element	Yes	Multiple Instances Supported
submission Element	Yes	method="put" in xforms:submission is not supported.
bind Element	Yes	Attribute p3ptype not supported.
xsd:schema Element	Yes
Must Understand	No
Extension Module	Yes

C.2 XForms Processing Model

Table C-2 Initialization Events

XForms Specification	Supported	Comments
xforms-model-construct	Yes
xforms-model-initialize	Yes
xforms-initialize-done	Yes
xforms-ui-initialize	Yes
xforms-form-control-initialize	Yes
xforms-model-destruct	No

Table C-3 Interaction Events

XForms Specification	Supported	Comments
xforms-previous	No
xforms-next	No
xforms-focus	No
xforms-help	Yes	Supported where user agents support help events
xforms-hint	Yes	Supported where user agents support hint events
xforms-refresh	Yes
xforms-revalidate	Yes
xforms-recalculate	Yes
xforms-reset	Yes
xforms-submit	Yes

Table C-4 Notification Events

XForms Specification	Supported	Comments
DOMActivate	Yes
xforms-value-changing	No
xforms-value-changed	Yes
xforms-select	No
xforms-deselect	No
xforms-scroll-first	No
xforms-scroll-last	No
xforms-insert	No
xforms-delete	No
xforms-valid	Yes
xforms-invalid	Yes
DOMFocusIn	No
DOMFocusOut	No
xforms-readonly	Yes
xforms-readwrite	Yes
xforms-required	Yes
xforms-optional	Yes
xforms-enabled	Yes
xforms-disabled	Yes
xforms-submit-done	Yes
xforms-submit-error	Yes

Table C-5 Error Indications

XForms Specification	Supported	Comments
xforms-bind-exception	No
xforms-link-exception	No
xforms-link-error	No
xforms-compute-exception	No

C.3 DataTypes

Table C-6 Basic Data Types

XForms Specification	Supported	Comments
dateTime	Yes
time	Yes
date	Yes
gYearMonth	Yes
gYear	Yes
gMonthDay	Yes
gDay	Yes
gMonth	Yes
string	Yes
boolean	Yes
base64Binary	No
decimal	Yes
anyURI	Yes
integer	Yes
nonPositiveInteger	Yes
negativeInteger	Yes
long	Yes
int	Yes
short	Yes
byte	Yes
nonNegativeInteger	Yes
unsignedLong	Yes
unsignedInt	Yes
unsignedShort	Yes
unsignedByte	Yes
positiveInteger	Yes

Table C-7 XForms DataTypes

XForms Specification	Supported	Comments
xforms:listItem	Yes
xforms:listItems	Yes
xforms:dayTimeDuration	Yes
xforms:yearMonthDuration	Yes

Table C-8 Advanced and Derived DataTypes

XForms Specification	Supported	Comments
normalized String	No
hexBinary	No
float	No
double	No
QName	No
NOTATION	No
token	No
language	No
Name	No
NCName	No
ID	No
IDREF	No
IDREFS	No
ENTITY	No
ENTITIES	No
NMTOKEN	No
NMTOKENS	No

C.4 Model Item Properties And Schema Constraints

Table C-9 Model Item Properties

XForms Specification	Supported	Comments
type	Yes	Restricted to schema datatypes supported by the current implementation
readonly	Yes
required	Yes
relevant	Yes
calculate	Yes
constraint	Yes
maxOccurs	Yes
minOccurs	Yes
p3ptype	No

Table C-10 Schema Constraints

XForms Specification	Supported	Comments
Schema association	No
xsi:type	Yes
type attribute in Bind	Yes
default xsi:string	Yes

C.5 XPath Expression in XForms

Table C-11 XPath DataTypes, DOM Access and Evaluation Context

XForms Specification	Supported	Comments
XPath 1.0 Datatypes (boolean, string, number, node-set)	Yes
DOM Access to Instance Data	No
Evaluation Context	Yes

Table C-12 Binding Expressions

XForms Specification	Supported	Comments
Model Binding Expressions	Yes	Expression used in Model Item Propertied (bind element)
Dynamic dependences in Model Binding Expressions	No	XForms specifications does not allow dynamic dependencies in model binding expressions.
UI Binding Expressions	Yes
Dynamic dependencies in UI Binding Expressions	Yes	XForms can support dynamic binding expression in binding attributes of UI controls. OracleAS Wireless supports dynamic binding expressions in UI controls with exception of Voice rendering mode.

Table C-13 XPath Node Set Functions

XForms Specification	Supported	Comments
count()	Yes
id()1	Yes
last()1	Yes
position()1	Yes
name()1	Yes
local-name()1	Yes
namespace-uri()1	Yes
instance()1	Yes

Table C-14 XPath String Functions

XForms Specification	Supported	Comments
concat()	Yes
contains()	Yes
normalize-space()1	Yes
starts-with()	Yes
string()	Yes
string-length()	Yes
substring()	Yes
substring-after()	Yes
substring-before()	Yes
translate()	Yes
property()	No

Table C-15 XPath Number Functions

XForms Specification	Supported	Comments
ceiling()	Yes
floor()	Yes
number()	Yes
round()	Yes
sum()	Yes
avg()	Yes	Defined in XForms Specification
min()	Yes	Defined in XForms Specification
max()	Yes	Defined in XForms Specification
count-non-empty()1	Yes
index()	Yes	Defined in XForms Specification

Table C-16 XPath Boolean Functions

XForms Specification	Supported	Comments
boolean()	Yes
false()	Yes
lang()1	Yes
not()	Yes
true()	Yes
boolean-from-string()	Yes	Defined in XForms Specification
if()	Yes	Defined in XForms Specification

¹ These XPath functions must be used carefully in Voice (aural) mode. The Voice (aural) mode uses a scripting model to bring some actions to the client side for greater form interactivity. If these XPath functions are used in aural mode, the author should force the recalculation or revalidation on the server by using actions that require server-side support.

Table C-17 XForms/XPath Date and Time Functions

XForms Specification	Supported	Comments
now()	Yes	Defined in XForms Specification
days-from-date()	Yes	Defined in XForms Specification
seconds-from-dateTime()	Yes	Defined in XForms Specification
seconds()	Yes	Defined in XForms Specification
months()	Yes	Defined in XForms Specification

Table C-18 XPath Extension Functions

Extension Specification	Supported	Comments
current()	Yes	As defined in XSLT Specification current() function is useful when iterating inside the repeat. Returns the current node in the repeat nodeset. Note: If you change the context node using the ref/nodeset attribute (such as group, setvalue), current() will no longer return the current repeat node.

C.6 XForms UI Controls

Table C-19 Basic UI Controls

XForms Specification	Supported	Comments
input	Yes	navindex, accesskey, appearance attributes not supported. inputmode attribute not supported. Additional supported attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional supported attributes for style hints size, mxml:media
secret	Yes	navindex, accesskey, appearance, incremental attributes not supported. inputmode attribute not supported. Additional supported attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional supported attributes for style hints size, mxml:media
textarea	Yes	navindex, accesskey, appearance, incremental attributes not supported. inputmode attribute not supported. Additional supported attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional supported attributes for style hints rows, cols, mxml:media
output	Yes	appearance attributes not supported. Additional Extended attributes id, style, class Additional device style hints mxml:media
upload	No
range	No
trigger	Yes	navindex, accesskey, appearance attributes not supported. Additional Extended attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional device style hints mxml:media
submit	Yes	navindex, accesskey, appearance attributes not supported. Additional Extended attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional device style hints mxml:media
select	Yes	navindex, accesskey, appearance attributes not supported. selection attribute not supported. selection is always "closed" Select ui displays as a checkbox. Additional supported attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional supported attributes for style hints size, mxml:media
select1	Yes	navindex, accesskey, appearance attributes not supported. selection attribute not supported. selection is always "closed" Select ui displays as a radio button. Additional supported attributes id, style, class Additional supported attributes slot, modal (for aural/voice grammar) Additional supported attributes for style hints size, mxml:media
choices	Yes
item	Yes	help, hint, alert, actions on item is not supported
filename	No
mediatype	No
value	Yes	Only PCDATA, as child node, is supported by the value element.
label	Yes	Single Node binding attributes are not supported (Note: Can use <output> within label to embed values from instance). Linking attributes not supported
help	Yes	Single Node Binding attributes are not supported (Note: Can use <output> within help to embed values from instance). Linking attributes not supported
hint	Yes	Single Node Binding attributes are not supported (Note: Can use <output> within hint to embed values from instance). Linking attributes not supported
alert	Yes	Single Node Binding attributes are not supported (Note: Can use <output> within notification to embed values from instance). Linking attributes not supported
itemset	Yes	help, hint, alert, actions on itemset are not supported
copy	No	No
extension	Yes	<extension> element supports declaration of <grammar> for UI controls <extension> element supports <label> elements. This allows an UI control to have multiple Labels. These multiple <label>'s are played on a voice interface as extended prompt interface.

Table C-20 Advanced UI Controls

XForms Specification	Supported	Comments
group	Yes	navindex, accesskey, appearance attributes not supported.
repeat	Yes	navindex, accesskey, appearance attributes not supported. Nested repeats not supported
repeat Attributes	No
switch/case	Yes	navindex, accesskey, appearance attributes not supported.

Table C-21 Extension UIControls

Extension	Supported	Comments
mxml:uiobject	Yes	This is an extension UI Control defined in the MXML namespace. The "uiobject" element allows XForms applications to launch user interfaces defined in other languages, enabling reuse of existing applications defined in those languages. "uiobject" allows an XForms application to pass and receive parameters (form data) from the external user interface using the "uiparam" element. The content type of a "uiobject" is indicated by its "type" attribute. The URI of the external user interface is indicated by the <uiobject>'s "data" attribute, while its "method" and "enctype" attributes determine how the form data parameters are passed to the external user interface. The <uiobject>'s Single Node Binding attributes, as for XForms <group>, sets the XPath context for the <uiparam>'s child elements.
mxml:uiparam	Yes	This is an extension element defined in the MXML namespace which occurs as a child node of a <uiobject>. <uiparam> provides the ability to pass/receive instance data between an XForms instance and the <uiobject>. <uiparam> has single node binding attributes that map instance data to either an input value to the <uiobject> (if valuetype="in"), an output value from the <uiobject> (if valuetype="out"), or a submission parameter to the URI specified by the <uiobject>'s "data" attribute (if valuetype"submit"). The "name" attribute of <uiparam> identifies the parameter name in the external user interface that is associated with the instance data.
mxml:uieventmap	Yes	This is an extension element defined in the MXML namespace which occurs as a child of <uiobject>. <uieventmap> allows the author to map custom events thrown by the external user interface to XForms events.

Note: In this release, <uiobject> only supports launching of UI interfaces defined in VoiceXML. The <uiobject> that links to interfaces implemented in VoiceXML must have their type set to text/x-vxml.

C.7 XForms Actions

Table C-22 Basic UI Controls

XForms Specification	Supported	Comments
action	Yes	Deferred Updates Not Supported
dispatch	No
rebuild	No
recalculate	Yes
refresh	Yes
setfocus	Yes	Supported only on devices that support scripting or an XForms plugin. In this release, this is supported in Voice (aural) and Laptop devices.
load	Yes	show="new" not supported. Show="new" will behave just like show="replace"
setvalue	Yes
send	Yes
reset	Yes
message	Yes	src attribute not supported Single Node Binding attributes (bind/ref attribute) are not supported (Note: Can use <output> within help to embed values from instance).

Table C-23 Extension Actions

Extension	Supported	Comments
mxml:disconnect	Yes	Extension action defined in MXML namespace. OracleAS Wireless supports Voice Interface using a regular telephone and VoiceXML Gateway. This action performs a telephony call disconnect.
mxml:handler	Yes	Extension action defined in MXML namespace. This action supports XForms actions based on the nth occurrence of an event on a UI control.