RE: [xliff] XLIFF and Xforms

["Yves Savourel" <ysavourel@translate.com>]

Thanks for the input on XForms Andrzej. I'll integrate that in the "rought
first draft" of the HTML profile (which is due soon...)

Kenavo,
-yves


-----Original Message-----
From: Andrzej Zydron [mailto:azydron@xml-intl.com] 
Sent: Tuesday, February 03, 2004 11:54 AM
To: xliff@lists.oasis-open.org
Cc: tony.jewtushenko@oracle.com
Subject: [xliff] XLIFF and Xforms

Hi,

In response to the request from Tony to take a look at XForms and its
potential representation in XLIFF:

1) XForms is an official W3C recommendation. The full details of the
standard can be viewed at the following URL:

http://www.w3.org/TR/2003/REC-xforms-20031014/

2) Design goals
XForms was designed to make the coding of HTML/XHTML forms easier and to be
output independent. A well designed XForm is capable of being rendered in
VoiceXML as well as HTML, XHTML or as a valid/well formed XML document.

In addition validating constraints can be specified for input values -
something which requires extensive scripting in HTML.

The goal of XForms is to provide the 20% of necessary functionality in order
to eliminate 80% of the need for scripting.

An XForm processor is needed to render an XForm into an instance.

3) Controls

XForms contain the following controls (HTML equivalents described
alongside):

3.1) <input> (HTML equivalent: <input type="text">) - For entry of small
amounts of text
3.2) <textarea> (HTML equivalent: <textarea>) - For entry of large amounts
of text
3.3) <secret> (HTML equivalent: <input type="password">) - For entry of
sensitive information
3.4) <output> (HTML equivalent: N/A) - For inline display of any instance
data
3.5) <range> (HTML equivalent: N/A) - For smooth "volume control" 
selection of a value
3.6) <upload> (HTML equivalent: <input type="file">) - For upload of file or
device data
3.7) <trigger> (HTML equivalent: <button>) - For activation of form events
3.8) <submit> (HTML equivalent: <input type="submit">) - For submission of
form data
3.9) <select> (HTML equivalent: <select multiple="multiple"> or multiple
<input type="checkbox">) - For selection of zero, one, or many options
3.10) <select1> (HTML equivalent: <select> or multiple <input type="radio">)
- For selection of just one option among several

4) Structure

Each instance of a form is always preceded by a <model> element which
defines the submission action and method e.g.:

<model>
    <submission action="http://example.com/search";
                method="get"
                id="s"/>
</model>

The actual instance must refer back to the submission model via the
"submission" attribute e.g.:

<input ref="q"><label>Find</label></input>
<submit submission="s"><label>Go</label></submit>

5) Translatable text.
The good news is that all translatable text within an XForm is always
contained in only one element: <label> e.g.:

<input ref="firstname"><label>First name:</label></input>

The <label> element is always a direct child of a control element.

6) Sources:

a. Three very good articles on XForms from xml.com: 
http://www.xml.com/pub/a/2001/09/05/xforms.htm
http://www.xml.com/pub/a/2003/09/10/xforms.html
http://www.xml.com/pub/a/2003/12/30/xforms.html

b. The official w3c.org pages for Xforms:
http://www.w3c.org/MarkUp/Forms

c. O'Reilly book:
XForms Essentials ISBN: 0-596-00369-2


I am not sure if I can submit email directly to the XLIFF list so I have
cc'ed Tony just in case.

Regards,

AZ


-- 


email - azydron@xml-intl.com
smail - Mr. A.Zydron
         24 Maybrook Gardens,
         High Wycombe,
         Bucks HP13 6PJ
Mobile +(44) 7966 477181
FAX    +(44) 870 831 8868
www - http://www.xml-intl.com

This message contains confidential information and is intended only for the
individual named.  If you are not the named addressee you may not
disseminate, distribute or copy this e-mail.  Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses.  The sender therefore does not accept
liability for any errors or omissions in the contents of this message which
arise as a result of e-mail transmission.  If verification is required
please request a hard-copy version. Unless explicitly stated otherwise this
message is provided for informational purposes only and should not be
construed as a solicitation or offer.





To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xliff/members/leave_workgroup.p
hp.