Tuukka Haapaniemi26.11.2008

XForms – What’s the need?HTML forms

Very outdatedHard to develop and to maintainRequires lot of work

To create basic validation To create basic calculations In effect, to make anything userfriendly’ish

26.11.2008 2Future of XForms - Tuukka Haapaniemi

Limitations of HTML formsProvides no means of separating data from

the viewData insertion into the templated form

Client -> Server ideologyHard to implement workflow

Flat, key-value paired data

26.11.2008 Future of XForms - Tuukka Haapaniemi 3

Key ideas of XFormsSeparation of data from views of data

Model View Controller –patternReferencing complex data easily from the

viewWorkflow by changing only the viewSimple calculationsSimple validationsDynamic controlsDevice specific rendering

26.11.2008 Future of XForms - Tuukka Haapaniemi 4

XForms’ requirementsXML namespacesXML XchemaXpathXML events CSS3

26.11.2008 Future of XForms - Tuukka Haapaniemi 5

How to use XForms nowBrowser specific plug-in

Common users propably don’t want to download

Server side XForms engineOrbeon FormsMany others

Client side parsingUbiquity XFormsMany others

26.11.2008 Future of XForms - Tuukka Haapaniemi 6

Server side XForms engineNo need for a separately downloaded plug-inSimilar idea as with PHP, ASP(.NET) etc.

Produce currently supported code, that is, HTML, JavaScript and CSS from the XFoms code on the server

Emulation layer creates extra payload on server

Multiple postbacks or heavy custom scripting required

26.11.2008 Future of XForms - Tuukka Haapaniemi 7

Client side parsingNo need for a separately downloaded plug-inBy using existing JavaScript libraries and

adding new APIs to them, parse the XForms code on client

Light on the serverA bit slower on the clientAjax support – less full postbacks requiredHard to make cross-platform and cross-

browser compatible

26.11.2008 Future of XForms - Tuukka Haapaniemi 8

Near future of XFormsCurrent implementations allow to test and learn

the technologyNew applications can be created with XForms

and used through the existing implementationsEasy to transform if/when native support arrivesIntelligent usage of supported technologies

possibleStrong ground through being a W3C standard

26.11.2008 Future of XForms - Tuukka Haapaniemi 9

Future of native XFormsFireFox

Has a good plug-in created close to the browsers coreImplements most of XForms’ requirementsIs constantly rising in ”market share” (44%, Oct 2008)

Microsoft Internet ExplorerHas one of the best plug-insMicrosoft has a competing product: InfoPathCould lose its market leader status (47,1%, Oct 2008)

Opera and Apple unenthusiastic

26.11.2008 Future of XForms - Tuukka Haapaniemi 10

Questions & discussion

26.11.2008 Future of XForms - Tuukka Haapaniemi 11

Thank you!

26.11.2008 Future of XForms - Tuukka Haapaniemi 12